From: Rahul Rameshbabu <sergeantsagara@protonmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: rust-for-linux@vger.kernel.org, linux-pci@vger.kernel.org,
"Danilo Krummrich" <dakr@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>
Subject: Re: [PATCH] rust: pci: fix incorrect platform references in doc comments
Date: Sun, 14 Sep 2025 03:26:54 +0000 [thread overview]
Message-ID: <87ikhlr9xl.fsf@protonmail.com> (raw)
In-Reply-To: <CANiq72msM5PT2mYKrX_RPXYtA4vapMRO=iSex1gQZqiXdpvvDA@mail.gmail.com>
On Sat, 13 Sep, 2025 21:08:46 +0200 "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com> wrote:
> On Sat, Sep 13, 2025 at 7:26 PM Rahul Rameshbabu
> <sergeantsagara@protonmail.com> wrote:
>>
>> Fixes: 1bd8b6b2c5d3 ("rust: pci: add basic PCI device / driver abstractions")
>> Fixes: 18ebb25dfa18 ("rust: pci: implement Driver::unbind()")
>
> These do not point to the same set of stable releases -- one cannot be
> backported to 6.16. In these cases, it is best to split the fix into
> two.
>
> And in the one that can be, you probably want to add Cc: stable so
> that Greg's bot doesn't detect it :)
Thanks Miguel! Just sent out the two patches.
>
> Thanks!
>
> Cheers,
> Miguel
next prev parent reply other threads:[~2025-09-14 3:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-13 17:26 [PATCH] rust: pci: fix incorrect platform references in doc comments Rahul Rameshbabu
2025-09-13 19:08 ` Miguel Ojeda
2025-09-14 3:26 ` Rahul Rameshbabu [this message]
2025-09-15 5:29 ` Manivannan Sadhasivam
2025-09-15 6:28 ` Miguel Ojeda
2025-09-15 6:58 ` Manivannan Sadhasivam
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=87ikhlr9xl.fsf@protonmail.com \
--to=sergeantsagara@protonmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bhelgaas@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=kwilczynski@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox