From: Andreas Hindborg <a.hindborg@kernel.org>
To: "Daniel Almeida" <daniel.almeida@collabora.com>
Cc: "Christian Schrefl" <chrisi.schrefl@gmail.com>,
<ojeda@kernel.org>, <alex.gaynor@gmail.com>,
<boqun.feng@gmail.com>, <gary@garyguo.net>,
<bjorn3_gh@protonmail.com>, <benno.lossin@proton.me>,
<tmgross@umich.edu>, <rust-for-linux@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>
Subject: Re: [PATCH v2] rust: irq: add support for request_irq()
Date: Tue, 04 Mar 2025 14:05:23 +0100 [thread overview]
Message-ID: <87o6yhgd4c.fsf@kernel.org> (raw)
In-Reply-To: <30401DE8-53DA-4CF3-9D97-1511015BCD4D@collabora.com> (Daniel Almeida's message of "Thu, 23 Jan 2025 13:27:35 -0300")
"Daniel Almeida" <daniel.almeida@collabora.com> writes:
> Hi Christian,
>
>> On 23 Jan 2025, at 13:00, Christian Schrefl <chrisi.schrefl@gmail.com> wrote:
>>
>> On 22.01.25 5:39 PM, Daniel Almeida wrote:
>>> Add support for registering IRQ handlers in Rust.
[...]
>>> +/// The flags that can be used when registering an IRQ handler.
>>> +pub mod flags {
>>
>> Maybe move flags into a separate file?
>> You even have a directory for irq.
>
> Why? Most flags are defined in the same file. See alloc::flags, for example.
>
> I am not against this, but since this is merely aesthetic in nature, we should maybe
> wait for input from more people.
I would prefer them in another file as well. Not a hard requirement though.
[...]
>>> +/// // This will run (in a separate kthread) iff `handle_irq` returns
>> typo iff
>
> I mean the acronym for “if and only if”.
Since it is not immediately obvious to all readers, prefer "if and only
if". I think we discussed this at pin-init patches a long while ago.
Best regards,
Andreas Hindborg
next prev parent reply other threads:[~2025-03-04 13:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <u-vC1KbeOK3Fd2PClzinb8LmqS_dntOW-pOSmZIFWotCZeTOg30xR_GYUc4oReAKZeuuu7ZaXWzfeTkpGMlr0A==@protonmail.internalid>
2025-01-22 16:39 ` [PATCH v2] rust: irq: add support for request_irq() Daniel Almeida
2025-01-23 7:17 ` Boqun Feng
2025-01-23 9:07 ` Alice Ryhl
2025-05-14 14:44 ` Daniel Almeida
2025-05-15 17:17 ` Christian Schrefl
2025-01-23 16:00 ` Christian Schrefl
2025-01-23 16:27 ` Daniel Almeida
2025-01-23 17:09 ` Christian Schrefl
2025-03-04 13:05 ` Andreas Hindborg [this message]
2025-02-10 8:41 ` Daniel Almeida
2025-02-10 16:41 ` Guangbo Cui
2025-03-04 13:11 ` Andreas Hindborg
2025-03-04 13:43 ` Andreas Hindborg
2025-03-04 16:48 ` Daniel Almeida
2025-03-17 14:58 ` Alice Ryhl
2025-05-09 13:58 ` Daniel Almeida
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=87o6yhgd4c.fsf@kernel.org \
--to=a.hindborg@kernel.org \
--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=chrisi.schrefl@gmail.com \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.