From: Simon Horman <horms@kernel.org>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>, Andrew Lunn <andrew+netdev@lunn.ch>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 3/3] net: phy: fixed_phy: constify status argument where possible
Date: Tue, 20 May 2025 08:21:47 +0100 [thread overview]
Message-ID: <20250520072147.GP365796@horms.kernel.org> (raw)
In-Reply-To: <d1764b62-8538-408b-a4e3-b63715481a38@gmail.com>
On Sat, May 17, 2025 at 10:37:29PM +0200, Heiner Kallweit wrote:
> Constify the passed struct fixed_phy_status *status where possible.
>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2025-05-20 7:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-17 20:33 [PATCH net-next 0/3] net: phy: fixed_phy: simplifications and improvements Heiner Kallweit
2025-05-17 20:34 ` [PATCH net-next 1/3] net: phy: fixed_phy: remove irq argument from fixed_phy_add Heiner Kallweit
2025-05-20 7:21 ` Simon Horman
2025-05-20 17:57 ` Florian Fainelli
2025-05-20 23:29 ` Greg Ungerer
2025-05-17 20:35 ` [PATCH net-next 2/3] net: phy: fixed_phy: remove irq argument from fixed_phy_register Heiner Kallweit
2025-05-20 7:21 ` Simon Horman
2025-05-20 17:59 ` Florian Fainelli
2025-05-17 20:37 ` [PATCH net-next 3/3] net: phy: fixed_phy: constify status argument where possible Heiner Kallweit
2025-05-20 7:21 ` Simon Horman [this message]
2025-05-20 18:02 ` Florian Fainelli
2025-05-21 1:20 ` [PATCH net-next 0/3] net: phy: fixed_phy: simplifications and improvements patchwork-bot+netdevbpf
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=20250520072147.GP365796@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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.