[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72mq4qcuT-h-gBsVfL=D2DJvzXDL8dQwxif5AWiqd4=vig@mail.gmail.com>
Date: Mon, 26 Jan 2026 14:24:51 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: 하승종 <engineer.jjhama@...il.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Miguel Ojeda <ojeda@...nel.org>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <lossin@...nel.org>, Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
Danilo Krummrich <dakr@...nel.org>, Arnd Bergmann <arnd@...db.de>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC 0/3] rust: tty: introduce TTY subsystem abstractions
and rttyprintk
On Mon, Jan 26, 2026 at 2:13 PM 하승종 <engineer.jjhama@...il.com> wrote:
>
> To answer your question directly: I do not have a plan to implement a specific
> serial port driver at this moment.
> My motivation for this patch series was simply to fill the missing TTY subsystem
> gap in the Rust for Linux project. I believed that providing these abstractions
> would be valuable as foundational infrastructure, enabling future developers to
> write TTY-related drivers in Rust.
Yeah, as Greg says, the kernel needs a user for new code.
In these two pages I explain a bit the usual rules involved and some
general guidelines on how to proceed with new abstractions:
https://rust-for-linux.com/contributing#submitting-new-abstractions-and-modules
https://rust-for-linux.com/rust-reference-drivers
I hope that helps, and thanks for contributing -- a reference
implementation is always good to have in the list :)
Cheers,
Miguel
Powered by blists - more mailing lists