From: Andrew Lunn <andrew@lunn.ch>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: "FUJITA Tomonori" <fujita.tomonori@gmail.com>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Trevor Gross" <tmgross@umich.edu>,
netdev@vger.kernel.org, rust-for-linux@vger.kernel.org,
"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>,
"Danilo Krummrich" <dakr@kernel.org>,
linux-kernel@vger.kernel.org, patches@lists.linux.dev
Subject: Re: [PATCH 1/3] rust: net: phy: fix example's references to `C{22,45}`
Date: Mon, 10 Nov 2025 16:50:06 +0100 [thread overview]
Message-ID: <ebc83a89-b13c-49ae-adc3-c8de6903b735@lunn.ch> (raw)
In-Reply-To: <20251110122223.1677654-1-ojeda@kernel.org>
On Mon, Nov 10, 2025 at 01:22:21PM +0100, Miguel Ojeda wrote:
> The example refers to `phy::C{22,45}`, but there are no such items --
> they are within `reg`.
>
> Thus fix it.
>
> Fixes: 5114e05a3cfa ("rust: net::phy unified genphy_read_status function for C22 and C45 registers")
> Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
> ---
> Please feel free to drop the Fixes tag -- I generally add them for
> things that get actually rendered in the documentation, since the stable
> team sometimes picks even typos, but it is of course not an bug on a
> kernel feature, of course.
netdev generally does backport documentation fixed. There are a lot of
developers stuck on LTS trees.
Please submit this to net, and include the Fixes tag.
Andrew
next prev parent reply other threads:[~2025-11-10 15:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 12:22 Miguel Ojeda
2025-11-10 12:22 ` [PATCH 2/3] rust: net: phy: make example buildable Miguel Ojeda
2025-11-10 23:34 ` FUJITA Tomonori
2025-11-11 21:02 ` Miguel Ojeda
2025-11-11 22:55 ` FUJITA Tomonori
2025-11-10 12:22 ` [PATCH 3/3] rust: net: phy: follow usual comment conventions Miguel Ojeda
2025-11-10 23:37 ` FUJITA Tomonori
2025-11-10 15:50 ` Andrew Lunn [this message]
2025-11-10 23:24 ` [PATCH 1/3] rust: net: phy: fix example's references to `C{22,45}` FUJITA Tomonori
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=ebc83a89-b13c-49ae-adc3-c8de6903b735@lunn.ch \
--to=andrew@lunn.ch \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=patches@lists.linux.dev \
--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
all inboxes | Powered by JetHome®