linux-kernel - Re: [PATCH 2/2] rust: pci: fix typo in Bar struct's comment

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <DFGNTT6HB593.2C2IGNSHV9B82@kernel.org>
Date: Mon, 05 Jan 2026 13:38:27 +0100
From: "Danilo Krummrich" <dakr@...nel.org>
To: "Miguel Ojeda" <miguel.ojeda.sandonis@...il.com>
Cc: "Greg KH" <gregkh@...uxfoundation.org>, <sashal@...nel.org>, "Marko
 Turk" <mt@...koturk.info>, "Dirk Behme" <dirk.behme@...il.com>,
 <dirk.behme@...bosch.com>, <linux-pci@...r.kernel.org>,
 <linux-kernel@...r.kernel.org>, <rust-for-linux@...r.kernel.org>,
 <stable@...r.kernel.org>
Subject: Re: [PATCH 2/2] rust: pci: fix typo in Bar struct's comment

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.