From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: FUJITA Tomonori <fujita.tomonori@gmail.com>
Cc: benno.lossin@proton.me, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH RFC v1] rust: add 'firmware' tag support to module! macro
Date: Fri, 26 Apr 2024 09:21:03 +0200 [thread overview]
Message-ID: <CANiq72k+GG=4NOxyAuiY8ears8Fii7G_i3Wkaa9vU1ywrryQSw@mail.gmail.com> (raw)
In-Reply-To: <20240426.101055.990464946230867124.fujita.tomonori@gmail.com>
On Fri, Apr 26, 2024 at 3:11 AM FUJITA Tomonori
<fujita.tomonori@gmail.com> wrote:
>
> - `firmware`: array of firmware names required by the kernel
I would say "file names", not just "names".
Cheers,
Miguel
next prev parent reply other threads:[~2024-04-26 7:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 13:53 [PATCH RFC v1] rust: add 'firmware' tag support to module! macro FUJITA Tomonori
2024-04-19 14:11 ` Greg KH
2024-04-19 16:41 ` Benno Lossin
2024-04-20 1:14 ` FUJITA Tomonori
2024-04-25 15:35 ` Benno Lossin
2024-04-26 1:10 ` FUJITA Tomonori
2024-04-26 7:11 ` Benno Lossin
2024-04-26 7:21 ` Miguel Ojeda [this message]
2024-04-26 9:40 ` FUJITA Tomonori
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='CANiq72k+GG=4NOxyAuiY8ears8Fii7G_i3Wkaa9vU1ywrryQSw@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=benno.lossin@proton.me \
--cc=fujita.tomonori@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
/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).