From: patchwork-bot+netdevbpf@kernel.org
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
alobakin@pm.me, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk
Subject: Re: [PATCH net-next] net: phy: fix up const issues in to_mdio_device() and to_phy_device()
Date: Wed, 28 May 2025 01:20:54 +0000 [thread overview]
Message-ID: <174839525499.1849945.743853526912527332.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <2025052246-conduit-glory-8fc9@gregkh>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 22 May 2025 13:21:47 +0200 you wrote:
> Both to_mdio_device() and to_phy_device() "throw away" the const pointer
> attribute passed to them and return a non-const pointer, which generally
> is not a good thing overall. Fix this up by using container_of_const()
> which was designed for this very problem.
>
> Cc: Alexander Lobakin <alobakin@pm.me>
> Cc: Andrew Lunn <andrew@lunn.ch>
> Cc: Heiner Kallweit <hkallweit1@gmail.com>
> Cc: Russell King <linux@armlinux.org.uk>
> Fixes: 7eab14de73a8 ("mdio, phy: fix -Wshadow warnings triggered by nested container_of()")
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> [...]
Here is the summary with links:
- [net-next] net: phy: fix up const issues in to_mdio_device() and to_phy_device()
https://git.kernel.org/netdev/net-next/c/e9cb929670a1
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:[~2025-05-28 1:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 11:21 [PATCH net-next] net: phy: fix up const issues in to_mdio_device() and to_phy_device() Greg Kroah-Hartman
2025-05-28 1:20 ` 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=174839525499.1849945.743853526912527332.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alobakin@pm.me \
--cc=andrew@lunn.ch \
--cc=gregkh@linuxfoundation.org \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@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 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.