From: Danilo Krummrich <dakr@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Benno Lossin <benno.lossin@proton.me>,
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,
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 v4 2/2] rust: add firmware abstractions
Date: Wed, 19 Jun 2024 13:33:04 +0200 [thread overview]
Message-ID: <ZnLB8KfIFpN5dlid@pollux> (raw)
In-Reply-To: <2024061900-outspoken-blast-a391@gregkh>
On Wed, Jun 19, 2024 at 12:43:55PM +0200, Greg KH wrote:
> On Wed, Jun 19, 2024 at 11:44:23AM +0200, Danilo Krummrich wrote:
> > Greg,
> >
> > Benno's comments provide some nice hints to further improve the safety comments.
> > Since I was notified that those patches hit your tree already, how do you want
> > to proceed?
>
> Please start by not top-posting :)
Well, I guess it kinda made sense in this case, since I wasn't replying to any
of the comments specifically.
>
> Anyway, patches on top of what is in my tree is fine, these are just
> comment updates, not any real broken issue to prevent the existing stuff
> from existing.
Ok, I'll send you another series for this including the changes for the
MAINTAINERS file.
- Danilo
>
> thanks,
>
> greg k-h
>
next prev parent reply other threads:[~2024-06-19 11:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 15:48 [PATCH v4 0/2] Rust abstractions for Device & Firmware Danilo Krummrich
2024-06-18 15:48 ` [PATCH v4 1/2] rust: add abstraction for struct device Danilo Krummrich
2024-06-19 8:53 ` Benno Lossin
2024-06-20 13:37 ` Gary Guo
2024-06-18 15:48 ` [PATCH v4 2/2] rust: add firmware abstractions Danilo Krummrich
2024-06-18 16:27 ` Boqun Feng
2024-06-19 8:58 ` Benno Lossin
2024-06-19 9:44 ` Danilo Krummrich
2024-06-19 10:43 ` Greg KH
2024-06-19 11:33 ` Danilo Krummrich [this message]
2024-06-20 13:36 ` Gary Guo
2024-06-20 13:43 ` Danilo Krummrich
2024-06-27 10:36 ` Gary Guo
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=ZnLB8KfIFpN5dlid@pollux \
--to=dakr@redhat.com \
--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=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=mcgrof@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.