From: patchwork-bot+netdevbpf@kernel.org
To: Chunfeng Song <springbreeze@stu.pku.edu.cn>
Cc: kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, netdev@vger.kernel.org,
rust-for-linux@vger.kernel.org, andrew@lunn.ch,
hkallweit1@gmail.com, rmk+kernel@armlinux.org.uk,
ojeda@kernel.org, boqun@kernel.org, gary@garyguo.net,
fujita.tomonori@gmail.com, tmgross@umich.edu,
stable@vger.kernel.org
Subject: Re: [PATCH net v6] rust: net: phy: fix off-by-one bit positions in device status accessors
Date: Tue, 15 Sep 2026 02:10:10 +0000 [thread overview]
Message-ID: <178943821064.1315233.963613512821734944.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260910055110.167110-1-springbreeze@stu.pku.edu.cn>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 10 Sep 2026 05:51:10 +0000 you wrote:
> The hand-written bitfield offsets in is_link_up(), is_autoneg_enabled()
> and is_autoneg_completed() were correct when the abstraction was
> merged: at that time autoneg, link, and autoneg_complete were at bits
> 13, 14, and 15 of struct phy_device's first bitfield unit. Commit
> 2796ff1e3dca ("net: phy: add flag is_genphy_driven to struct phy_device")
> later inserted is_genphy_driven just before autoneg, shifting the three
> fields up by one, so the accessors now read:
>
> [...]
Here is the summary with links:
- [net,v6] rust: net: phy: fix off-by-one bit positions in device status accessors
https://git.kernel.org/netdev/net/c/6fb0a9d9071f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-15 2:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 5:51 [PATCH net v6] rust: net: phy: fix off-by-one bit positions in device status accessors Chunfeng Song
2026-09-10 9:43 ` FUJITA Tomonori
2026-09-15 2:10 ` patchwork-bot+netdevbpf [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=178943821064.1315233.963613512821734944.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=boqun@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=rust-for-linux@vger.kernel.org \
--cc=springbreeze@stu.pku.edu.cn \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.