[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72=JU5yXnQemmuM0Vnp8NKNO2H+LcmtzzMU4Xn9tBMduJg@mail.gmail.com>
Date: Tue, 28 Jan 2025 23:00:23 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Timothy Garwood <gtimothy-dev@...tonmail.com>
Cc: Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>,
Andreas Hindborg <a.hindborg@...nel.org>, Boqun Feng <boqun.feng@...il.com>,
Gary Guo <gary@...yguo.net>, Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>, Alice Ryhl <aliceryhl@...gle.com>,
Trevor Gross <tmgross@...ch.edu>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC] rust: HrTimerMode replacement with bitfield_options macro
On Tue, Jan 28, 2025 at 10:23 PM Timothy Garwood
<gtimothy-dev@...tonmail.com> wrote:
>
> Even if this patch depends on something ([2]) the "real patch" does not depend on?
I think it is fine, as long as it is clearly mentioned that it is
meant as expository only.
If dependencies are an issue, another option that may give you more
freedom is simply replying to the original patch with the extra one,
so that they are linked at least in the same thread.
> I forgot one [1] reference for the first link. I'll fix it.
Ah, what I meant is that some of the text is line-wrapped, i.e. the
newline breaks are a bit strangely positioned in the main text and
e.g. after the `Link:` tags there are newlines that should not be
there.
> Thank you Miguel,
You're welcome!
Cheers,
Miguel
Powered by blists - more mailing lists