From: Masahiro Yamada <masahiroy@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Martin Rodriguez Reboredo" <yakoyoku@gmail.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@samsung.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Tom Rix" <trix@redhat.com>,
rust-for-linux@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [RFC PATCH 0/1] rust: crates in other kernel directories
Date: Mon, 23 Oct 2023 03:19:59 +0900 [thread overview]
Message-ID: <CAK7LNASWc8wn+wcf1qYPTtZvWx-VX27TwgdyimJ4kh1=4GBRcQ@mail.gmail.com> (raw)
In-Reply-To: <CANiq72mM2BeWtZNqhvnbA3XR_ArfAi3CG3oxMuu+C74rB0+mBA@mail.gmail.com>
On Mon, Oct 9, 2023 at 9:01 PM Miguel Ojeda
<miguel.ojeda.sandonis@gmail.com> wrote:
>
> On Sat, Oct 7, 2023 at 1:07 AM Martin Rodriguez Reboredo
> <yakoyoku@gmail.com> wrote:
> >
> > Well, there's the network PHY driver series that is stuck on this
> > topic, I (and probably others) have local work that have the same issue
>
> No, that series is not stuck on this.
>
> > and said general case might not arrive that soon. So it'd better to
> > start on a feature that will benefit API users right away and can be
> > updated to fit needs. That's what I think.
>
> If there is an in-tree use case that will really require a solution to
> this very soon, then please focus on explaining that (e.g. what "local
> work" do you have and what are your plans for landing it upstream?)
> and we will do our best to reschedule priorities or we can provide a
> workaround for the time being.
>
> In any case, please note that this RFC breaks the kernel build and
> does not really solve the overall issue.
>
> Cheers,
> Miguel
>
Does this rely on the assumption that usb.rlib is small enough
because usb.rlib will be linked to every usb driver.
So, usb.rlib is just a binding, not able to write the
subsystem code in Rust, correct?
--
Best Regards
Masahiro Yamada
prev parent reply other threads:[~2023-10-22 18:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 15:57 [RFC PATCH 0/1] rust: crates in other kernel directories Martin Rodriguez Reboredo
2023-10-06 15:57 ` [RFC PATCH 1/1] scripts: Build per module Rust crates Martin Rodriguez Reboredo
2023-10-22 16:21 ` Masahiro Yamada
2023-10-22 16:30 ` Miguel Ojeda
2023-10-23 0:45 ` Martin Rodriguez Reboredo
2023-10-06 21:13 ` [RFC PATCH 0/1] rust: crates in other kernel directories Miguel Ojeda
2023-10-06 23:07 ` Martin Rodriguez Reboredo
2023-10-09 12:01 ` Miguel Ojeda
2023-10-22 18:19 ` Masahiro Yamada [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='CAK7LNASWc8wn+wcf1qYPTtZvWx-VX27TwgdyimJ4kh1=4GBRcQ@mail.gmail.com' \
--to=masahiroy@kernel.org \
--cc=a.hindborg@samsung.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=gary@garyguo.net \
--cc=llvm@lists.linux.dev \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=trix@redhat.com \
--cc=wedsonaf@gmail.com \
--cc=yakoyoku@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).