From: FUJITA Tomonori <tomo@flapping.org>
To: aliceryhl@google.com
Cc: tomo@flapping.org, ojeda@kernel.org, tj@kernel.org,
a.hindborg@kernel.org, acourbot@nvidia.com,
bjorn3_gh@protonmail.com, boqun@kernel.org, dakr@kernel.org,
daniel.almeida@collabora.com, gary@garyguo.net,
jiangshanlai@gmail.com, lossin@kernel.org, tamird@kernel.org,
tmgross@umich.edu, work@onurozkan.dev,
rust-for-linux@vger.kernel.org, fujita.tomonori@gmail.com
Subject: Re: [PATCH v1] MAINTAINERS: add the Rust workqueue abstractions to WORKQUEUE
Date: Thu, 10 Sep 2026 06:11:09 +0900 (JST) [thread overview]
Message-ID: <20260910.061109.2299253227990158500.tomo@flapping.org> (raw)
In-Reply-To: <aqFhykfMYOhdcqSv@google.com>
On Wed, 9 Sep 2026 13:40:26 +0000
Alice Ryhl <aliceryhl@google.com> wrote:
> On Wed, Sep 09, 2026 at 07:43:13PM +0900, FUJITA Tomonori wrote:
>> From: FUJITA Tomonori <fujita.tomonori@gmail.com>
>>
>> rust/kernel/workqueue.rs and rust/helpers/workqueue.c hold the Rust
>> abstractions for the C workqueue API, but they are not listed in the
>> WORKQUEUE entry. Add them so that changes to the Rust side are also sent
>> to the workqueue maintainer.
>>
>> Signed-off-by: FUJITA Tomonori <fujita.tomonori@gmail.com>
>
> This is being fixed by:
> https://lore.kernel.org/all/20260807165252.3849875-4-dakr@kernel.org/
Thanks, I missed it. Please disregard this patch.
prev parent reply other threads:[~2026-09-09 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 10:43 [PATCH v1] MAINTAINERS: add the Rust workqueue abstractions to WORKQUEUE FUJITA Tomonori
2026-09-09 13:40 ` Alice Ryhl
2026-09-09 21:11 ` FUJITA Tomonori [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=20260910.061109.2299253227990158500.tomo@flapping.org \
--to=tomo@flapping.org \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=jiangshanlai@gmail.com \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@kernel.org \
--cc=tj@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
/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