From: "Danilo Krummrich" <dakr@kernel.org>
To: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>
Cc: "Greg KH" <gregkh@linuxfoundation.org>, <sashal@kernel.org>,
"Marko Turk" <mt@markoturk.info>,
"Dirk Behme" <dirk.behme@gmail.com>, <dirk.behme@de.bosch.com>,
<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<rust-for-linux@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH 2/2] rust: pci: fix typo in Bar struct's comment
Date: Mon, 05 Jan 2026 13:38:27 +0100 [thread overview]
Message-ID: <DFGNTT6HB593.2C2IGNSHV9B82@kernel.org> (raw)
In-Reply-To: <CANiq72nrPiTmuFStm5fmOZZM8e_4TGHFyC_77+cSqPp8yC8nUQ@mail.gmail.com>
On Mon Jan 5, 2026 at 11:39 AM CET, Miguel Ojeda wrote:
> On my side, I am happy either way -- what I currently do is explicitly tag the
> ones that appear in docs. That way you can decide on your side.
This is how I handle it as well. For doc-comments I request a Fixes: tag to be
added and leave it to the stable team to decide.
Unless explicitly requested by the stable team (which obviously did not happen
so far) I do not send separate backport patches for typos when the upstream
commit does not apply though.
prev parent reply other threads:[~2026-01-05 12:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260103143119.96095-1-mt@markoturk.info>
[not found] ` <20260103143119.96095-2-mt@markoturk.info>
[not found] ` <DFF23OTZRIDS.2PZIV7D8AHWFA@kernel.org>
[not found] ` <84cc5699-f9ab-42b3-a1ea-15bf9bd80d19@gmail.com>
[not found] ` <aVmHGBop5OPlVVBa@vps.markoturk.info>
[not found] ` <CANiq72=t-U8JTH2JZxkQaW7sbYXjWLpkYkuMd_CuzLoJLbEvgQ@mail.gmail.com>
2026-01-04 14:08 ` [PATCH 2/2] rust: pci: fix typo in Bar struct's comment Danilo Krummrich
2026-01-04 18:30 ` Miguel Ojeda
2026-01-05 6:25 ` Greg KH
2026-01-05 10:39 ` Miguel Ojeda
2026-01-05 12:38 ` Danilo Krummrich [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=DFGNTT6HB593.2C2IGNSHV9B82@kernel.org \
--to=dakr@kernel.org \
--cc=dirk.behme@de.bosch.com \
--cc=dirk.behme@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mt@markoturk.info \
--cc=rust-for-linux@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@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