From: Huacai Chen <chenhuacai@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "WANG Rui" <wangrui@loongson.cn>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Jonathan Corbet" <corbet@lwn.net>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@samsung.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"WANG Xuerui" <kernel@xen0n.name>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
loongarch@lists.linux.dev, linux-doc@vger.kernel.org,
loongson-kernel@lists.loongnix.cn
Subject: Re: [PATCH v1 0/2] Rust enablement for LoongArch
Date: Wed, 17 Jan 2024 12:34:29 +0800 [thread overview]
Message-ID: <CAAhV-H4-dfBN3icg6kczRiZ67DOX66M-vXXCrz7Me0iunp8kRA@mail.gmail.com> (raw)
In-Reply-To: <CANiq72nv3Uw8GLNqbdGBC3b+viF+o8BeppS9KWhpzBFvjqZLUg@mail.gmail.com>
Hi, Miguel,
On Tue, Jan 16, 2024 at 11:16 PM Miguel Ojeda
<miguel.ojeda.sandonis@gmail.com> wrote:
>
> On Tue, Jan 16, 2024 at 10:31 AM Huacai Chen <chenhuacai@kernel.org> wrote:
> >
> > OK, since Linus said the merge window is paused now, I rebase and
> > retag my tree and the Rust commit is like this, I think this is
> > perfect now?
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/chenhuacai/linux-loongson.git/commit/?h=loongarch-next&id=706f9e1ab7c7a58d80ef2c87d8720131253a2256
>
> Thanks a lot! That works, yeah.
>
> I also took the chance to build LLVM and QEMU and I tested the tag --
> it seems to work: I see the samples (built-in) printing in the kernel
> log :)
>
> So in case you end up rebasing for another reason and want to add it,
> even if it is a simple check I did:
>
> Tested-by: Miguel Ojeda <ojeda@kernel.org>
OK, if Xuerui updates this patch, then I will rebase again.
https://lore.kernel.org/loongarch/CAAhV-H7KteJvRVpj3Hz-Ui9VnmijcJq5D1Tb-KJvqTO_+jjp2Q@mail.gmail.com/T/#t
Huacai
>
> Cheers,
> Miguel
prev parent reply other threads:[~2024-01-17 4:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 3:21 [PATCH v1 0/2] Rust enablement for LoongArch WANG Rui
2024-01-08 3:21 ` [PATCH v1 1/2] Documentation: rust: Add a character to the first column WANG Rui
2024-01-08 3:21 ` [PATCH v1 2/2] LoongArch: Enable initial Rust support WANG Rui
2024-01-08 4:23 ` [PATCH v1 0/2] Rust enablement for LoongArch Huacai Chen
2024-01-09 9:54 ` Huacai Chen
2024-01-09 19:33 ` Boqun Feng
2024-01-10 1:41 ` WANG Rui
2024-01-10 2:09 ` Boqun Feng
2024-01-10 2:29 ` WANG Rui
2024-01-10 10:49 ` Miguel Ojeda
2024-01-11 3:16 ` WANG Rui
2024-01-14 15:43 ` Miguel Ojeda
2024-01-15 3:23 ` Huacai Chen
2024-01-15 16:08 ` Miguel Ojeda
2024-01-16 9:31 ` Huacai Chen
2024-01-16 15:15 ` Miguel Ojeda
2024-01-17 4:34 ` Huacai Chen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAhV-H4-dfBN3icg6kczRiZ67DOX66M-vXXCrz7Me0iunp8kRA@mail.gmail.com \
--to=chenhuacai@kernel.org \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=gary@garyguo.net \
--cc=kernel@xen0n.name \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=wangrui@loongson.cn \
--cc=wedsonaf@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).