From: Greg KH <gregkh@linuxfoundation.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Danilo Krummrich <dakr@redhat.com>,
rafael@kernel.org, mcgrof@kernel.org, russ.weight@linux.dev,
ojeda@kernel.org, alex.gaynor@gmail.com, wedsonaf@gmail.com,
boqun.feng@gmail.com, gary@garyguo.net, bjorn3_gh@protonmail.com,
benno.lossin@proton.me, a.hindborg@samsung.com,
aliceryhl@google.com, airlied@gmail.com,
fujita.tomonori@gmail.com, pstanner@redhat.com,
ajanulgu@redhat.com, lyude@redhat.com,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] rust: add abstraction for struct device
Date: Tue, 18 Jun 2024 10:57:31 +0200 [thread overview]
Message-ID: <2024061823-atrophy-definite-c139@gregkh> (raw)
In-Reply-To: <CANiq72kwROB8=HdmcbU49csAixKZkxfUUry7umZbpzPRUZ+3BA@mail.gmail.com>
On Tue, Jun 18, 2024 at 10:31:03AM +0200, Miguel Ojeda wrote:
> On Tue, Jun 18, 2024 at 7:32 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > Wait, I should just take this in my driver-core tree, right? Any
>
> That would be ideal, yeah. Thanks!
>
> > objections for me taking both of these there now for 6.11-rc1 inclusion?
>
> Perhaps give it a couple days to see if any last minute feedback comes
> (and given Boqun's in 2/2, I think Danilo may want to send a quick
> v4).
Ok, I'll wait a bit, thanks.
greg k-h
next prev parent reply other threads:[~2024-06-18 8:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 20:29 [PATCH v3 0/2] Rust abstractions for Device & Firmware Danilo Krummrich
2024-06-17 20:29 ` [PATCH v3 1/2] rust: add abstraction for struct device Danilo Krummrich
2024-06-18 5:31 ` Greg KH
2024-06-18 5:32 ` Greg KH
2024-06-18 8:31 ` Miguel Ojeda
2024-06-18 8:57 ` Greg KH [this message]
2024-06-17 20:29 ` [PATCH v3 2/2] rust: add firmware abstractions Danilo Krummrich
2024-06-17 22:05 ` Boqun Feng
2024-06-17 22:50 ` Danilo Krummrich
2024-06-17 23:00 ` Boqun Feng
2025-08-05 17:12 ` Andreas Hindborg
2024-06-18 19:47 ` Luis Chamberlain
2024-06-18 21:15 ` Danilo Krummrich
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=2024061823-atrophy-definite-c139@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=a.hindborg@samsung.com \
--cc=airlied@gmail.com \
--cc=ajanulgu@redhat.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=dakr@redhat.com \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=mcgrof@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=pstanner@redhat.com \
--cc=rafael@kernel.org \
--cc=russ.weight@linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--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 NNTP newsgroup(s).