From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: phylink: constify fwnode arguments
Date: Sat, 13 May 2023 20:00:20 +0000 [thread overview]
Message-ID: <168400802041.779.10634623968966547726.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <E1pxW6H-002QFs-SG@rmk-PC.armlinux.org.uk>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 12 May 2023 17:58:37 +0100 you wrote:
> Both phylink_create() and phylink_fwnode_phy_connect() do not modify
> the fwnode argument that they are passed, so lets constify these.
>
> Reviewed-by: Simon Horman <simon.horman@corigine.com>
> Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
> ---
> drivers/net/phy/phylink.c | 11 ++++++-----
> include/linux/phylink.h | 9 +++++----
> 2 files changed, 11 insertions(+), 9 deletions(-)
Here is the summary with links:
- [net-next] net: phylink: constify fwnode arguments
https://git.kernel.org/netdev/net-next/c/a0b7955310a4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-05-13 20:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 16:58 [PATCH net-next] net: phylink: constify fwnode arguments Russell King (Oracle)
2023-05-13 20:00 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-10 11:03 Russell King (Oracle)
2023-05-10 11:42 ` Simon Horman
2023-05-10 13:59 ` Andy Shevchenko
2023-05-11 11:29 ` Paolo Abeni
2023-05-11 11:32 ` Russell King (Oracle)
2023-05-11 13:47 ` Paolo Abeni
2023-05-11 15:31 ` Russell King (Oracle)
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=168400802041.779.10634623968966547726.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).