From: Matthew Wood <thepacketgeek@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Breno Leito" <leitao@debian.org>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] rust: console: add abstraction for kernel console drivers
Date: Fri, 27 Feb 2026 15:44:45 -0800 [thread overview]
Message-ID: <aaIrV3m41n-0mWxJ@deathstar> (raw)
In-Reply-To: <2026022704-xbox-comfort-2493@gregkh>
On Fri, Feb 27, 2026 at 06:14:43PM -0500, Greg Kroah-Hartman wrote:
> > This abstraction is a dependency for a Rust netconsole implementation
> > I am working on.
>
> I'd prefer to see it then, with the user, before even reviewing this
> one, sorry. That way we "know" it at least works for you.
>
Thanks for the reply Greg, that's a very fair request. Since the
complete netconsole Rust implementation crosses several subsytems
(module-support, net, configfs, console) and I haven't yet
submitted such a large series before:
1) Should I submit the complete implementation w/ dependencies as one
series?
2) If I create and include a minimum-viable functional example using
this console abstraction, would that suffice?
Regards,
Matthew
next prev parent reply other threads:[~2026-02-27 23:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 21:53 [PATCH v1] rust: console: add abstraction for kernel console drivers Matthew Wood
2026-02-27 23:14 ` Greg Kroah-Hartman
2026-02-27 23:44 ` Matthew Wood [this message]
2026-02-28 0:17 ` Miguel Ojeda
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=aaIrV3m41n-0mWxJ@deathstar \
--to=thepacketgeek@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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