From: "Danilo Krummrich" <dakr@kernel.org>
To: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>
Cc: "Alexandre Courbot" <acourbot@nvidia.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Yury Norov" <yury.norov@gmail.com>,
"John Hubbard" <jhubbard@nvidia.com>,
"Alistair Popple" <apopple@nvidia.com>,
"Joel Fernandes" <joelagnelf@nvidia.com>,
"Timur Tabi" <ttabi@nvidia.com>, "Edwin Peer" <epeer@nvidia.com>,
"Eliot Courtney" <ecourtney@nvidia.com>,
"Dirk Behme" <dirk.behme@de.bosch.com>,
"Steven Price" <steven.price@arm.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/6] rust: add `register!` macro
Date: Mon, 26 Jan 2026 15:24:52 +0100 [thread overview]
Message-ID: <DFYL8QGPXY92.3NPF5MTDSUZNE@kernel.org> (raw)
In-Reply-To: <CANiq72=AsoyN=+K8Tg3+zrK95ET0SyKaLFjzukxbMR1AbSk9vA@mail.gmail.com>
On Mon Jan 26, 2026 at 2:56 PM CET, Miguel Ojeda wrote:
> On Mon, Jan 26, 2026 at 2:29 PM Alexandre Courbot <acourbot@nvidia.com> wrote:
>>
>> This patchset is based on `driver-core-next`.
>
> I think in the end you wanted to pick this through driver-core in this
> cycle, right?
Yes, if the series is ready until -rc8.
> I have sent Acked-by's for that, I hope it helps.
Thanks!
>> Note that it also need `rust-fixes` to avoid an `unused_unsafe` warning.
>
> That sounds fine, i.e. -next has it and Linus will have it before the
> merge window (unless you want to get rid of the warnings in your own
> branch).
Exactly, having this warning in the driver-core tree intermediately is fine with
me.
- Danilo
prev parent reply other threads:[~2026-01-26 14:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 13:28 [PATCH v3 0/6] rust: add `register!` macro Alexandre Courbot
2026-01-26 13:28 ` [PATCH v3 1/6] rust: enable the `generic_arg_infer` feature Alexandre Courbot
2026-01-26 13:32 ` Gary Guo
2026-01-26 13:55 ` Miguel Ojeda
2026-01-26 13:28 ` [PATCH v3 2/6] rust: num: add `shr` and `shl` methods to `Bounded` Alexandre Courbot
2026-01-26 13:55 ` Miguel Ojeda
2026-01-26 13:28 ` [PATCH v3 3/6] rust: num: add `as_bool` method to `Bounded<_, 1>` Alexandre Courbot
2026-01-26 13:55 ` Miguel Ojeda
2026-01-26 13:28 ` [PATCH v3 4/6] rust: io: add `register!` macro Alexandre Courbot
2026-01-26 13:28 ` [PATCH v3 5/6] sample: rust: pci: use " Alexandre Courbot
2026-01-26 13:28 ` [PATCH FOR REFERENCE v3 6/6] gpu: nova-core: use the kernel " Alexandre Courbot
2026-01-26 13:56 ` [PATCH v3 0/6] rust: add " Miguel Ojeda
2026-01-26 14:24 ` Danilo Krummrich [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=DFYL8QGPXY92.3NPF5MTDSUZNE@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=apopple@nvidia.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=daniel.almeida@collabora.com \
--cc=dirk.behme@de.bosch.com \
--cc=ecourtney@nvidia.com \
--cc=epeer@nvidia.com \
--cc=gary@garyguo.net \
--cc=jhubbard@nvidia.com \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=steven.price@arm.com \
--cc=tmgross@umich.edu \
--cc=ttabi@nvidia.com \
--cc=yury.norov@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