* [PATCH net-next] Documentation: networking: Add missing PHY_GET command in the message list
@ 2024-10-23 14:15 Kory Maincent
2024-10-24 14:52 ` Simon Horman
0 siblings, 1 reply; 5+ messages in thread
From: Kory Maincent @ 2024-10-23 14:15 UTC (permalink / raw)
To: netdev, linux-doc, linux-kernel
Cc: Maxime Chevallier, Kory Maincent, thomas.petazzoni,
David S. Miller, Eric Dumazet, Jakub Kicinski, Paolo Abeni,
Jonathan Corbet
ETHTOOL_MSG_PHY_GET/GET_REPLY/NTF is missing in the ethtool message list.
Add it to the ethool netlink documentation.
Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
---
Documentation/networking/ethtool-netlink.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/networking/ethtool-netlink.rst b/Documentation/networking/ethtool-netlink.rst
index 295563e91082..70ecc3821007 100644
--- a/Documentation/networking/ethtool-netlink.rst
+++ b/Documentation/networking/ethtool-netlink.rst
@@ -236,6 +236,7 @@ Userspace to kernel:
``ETHTOOL_MSG_MM_GET`` get MAC merge layer state
``ETHTOOL_MSG_MM_SET`` set MAC merge layer parameters
``ETHTOOL_MSG_MODULE_FW_FLASH_ACT`` flash transceiver module firmware
+ ``ETHTOOL_MSG_PHY_GET`` get Ethernet PHY information
===================================== =================================
Kernel to userspace:
@@ -283,6 +284,8 @@ Kernel to userspace:
``ETHTOOL_MSG_PLCA_NTF`` PLCA RS parameters
``ETHTOOL_MSG_MM_GET_REPLY`` MAC merge layer status
``ETHTOOL_MSG_MODULE_FW_FLASH_NTF`` transceiver module flash updates
+ ``ETHTOOL_MSG_PHY_GET_REPLY`` Ethernet PHY information
+ ``ETHTOOL_MSG_PHY_NTF`` Ethernet PHY information
======================================== =================================
``GET`` requests are sent by userspace applications to retrieve device
--
2.34.1
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [PATCH net-next] Documentation: networking: Add missing PHY_GET command in the message list
2024-10-23 14:15 [PATCH net-next] Documentation: networking: Add missing PHY_GET command in the message list Kory Maincent
@ 2024-10-24 14:52 ` Simon Horman
2024-10-24 15:18 ` Kory Maincent
0 siblings, 1 reply; 5+ messages in thread
From: Simon Horman @ 2024-10-24 14:52 UTC (permalink / raw)
To: Kory Maincent
Cc: netdev, linux-doc, linux-kernel, Maxime Chevallier,
thomas.petazzoni, David S. Miller, Eric Dumazet, Jakub Kicinski,
Paolo Abeni, Jonathan Corbet
On Wed, Oct 23, 2024 at 04:15:58PM +0200, Kory Maincent wrote:
> ETHTOOL_MSG_PHY_GET/GET_REPLY/NTF is missing in the ethtool message list.
> Add it to the ethool netlink documentation.
>
> Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
> ---
> Documentation/networking/ethtool-netlink.rst | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/networking/ethtool-netlink.rst b/Documentation/networking/ethtool-netlink.rst
> index 295563e91082..70ecc3821007 100644
> --- a/Documentation/networking/ethtool-netlink.rst
> +++ b/Documentation/networking/ethtool-netlink.rst
> @@ -236,6 +236,7 @@ Userspace to kernel:
> ``ETHTOOL_MSG_MM_GET`` get MAC merge layer state
> ``ETHTOOL_MSG_MM_SET`` set MAC merge layer parameters
> ``ETHTOOL_MSG_MODULE_FW_FLASH_ACT`` flash transceiver module firmware
> + ``ETHTOOL_MSG_PHY_GET`` get Ethernet PHY information
> ===================================== =================================
>
> Kernel to userspace:
> @@ -283,6 +284,8 @@ Kernel to userspace:
> ``ETHTOOL_MSG_PLCA_NTF`` PLCA RS parameters
> ``ETHTOOL_MSG_MM_GET_REPLY`` MAC merge layer status
> ``ETHTOOL_MSG_MODULE_FW_FLASH_NTF`` transceiver module flash updates
> + ``ETHTOOL_MSG_PHY_GET_REPLY`` Ethernet PHY information
> + ``ETHTOOL_MSG_PHY_NTF`` Ethernet PHY information
I wonder if ETHTOOL_MSG_PHY_NTF should be removed.
It doesn't seem to be used anywhere.
> ======================================== =================================
>
> ``GET`` requests are sent by userspace applications to retrieve device
> --
> 2.34.1
>
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH net-next] Documentation: networking: Add missing PHY_GET command in the message list
2024-10-24 14:52 ` Simon Horman
@ 2024-10-24 15:18 ` Kory Maincent
2024-10-24 15:28 ` Simon Horman
0 siblings, 1 reply; 5+ messages in thread
From: Kory Maincent @ 2024-10-24 15:18 UTC (permalink / raw)
To: Simon Horman
Cc: netdev, linux-doc, linux-kernel, Maxime Chevallier,
thomas.petazzoni, David S. Miller, Eric Dumazet, Jakub Kicinski,
Paolo Abeni, Jonathan Corbet
On Thu, 24 Oct 2024 15:52:23 +0100
Simon Horman <horms@kernel.org> wrote:
> On Wed, Oct 23, 2024 at 04:15:58PM +0200, Kory Maincent wrote:
> > ETHTOOL_MSG_PHY_GET/GET_REPLY/NTF is missing in the ethtool message list.
> > Add it to the ethool netlink documentation.
> >
> > Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
> > ---
> > Documentation/networking/ethtool-netlink.rst | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/Documentation/networking/ethtool-netlink.rst
> > b/Documentation/networking/ethtool-netlink.rst index
> > 295563e91082..70ecc3821007 100644 ---
> > a/Documentation/networking/ethtool-netlink.rst +++
> > b/Documentation/networking/ethtool-netlink.rst @@ -236,6 +236,7 @@
> > Userspace to kernel: ``ETHTOOL_MSG_MM_GET`` get MAC merge
> > layer state ``ETHTOOL_MSG_MM_SET`` set MAC merge layer
> > parameters ``ETHTOOL_MSG_MODULE_FW_FLASH_ACT`` flash transceiver module
> > firmware
> > + ``ETHTOOL_MSG_PHY_GET`` get Ethernet PHY information
> > ===================================== =================================
> >
> > Kernel to userspace:
> > @@ -283,6 +284,8 @@ Kernel to userspace:
> > ``ETHTOOL_MSG_PLCA_NTF`` PLCA RS parameters
> > ``ETHTOOL_MSG_MM_GET_REPLY`` MAC merge layer status
> > ``ETHTOOL_MSG_MODULE_FW_FLASH_NTF`` transceiver module flash updates
> > + ``ETHTOOL_MSG_PHY_GET_REPLY`` Ethernet PHY information
> > + ``ETHTOOL_MSG_PHY_NTF`` Ethernet PHY information
>
> I wonder if ETHTOOL_MSG_PHY_NTF should be removed.
> It doesn't seem to be used anywhere.
We can't, as it is in the ethtool UAPI. Also I believe Maxime will use it on
later patch series. Maxime, you confirm?
Regards,
--
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH net-next] Documentation: networking: Add missing PHY_GET command in the message list
2024-10-24 15:18 ` Kory Maincent
@ 2024-10-24 15:28 ` Simon Horman
2024-10-24 16:11 ` Maxime Chevallier
0 siblings, 1 reply; 5+ messages in thread
From: Simon Horman @ 2024-10-24 15:28 UTC (permalink / raw)
To: Kory Maincent
Cc: netdev, linux-doc, linux-kernel, Maxime Chevallier,
thomas.petazzoni, David S. Miller, Eric Dumazet, Jakub Kicinski,
Paolo Abeni, Jonathan Corbet
On Thu, Oct 24, 2024 at 05:18:02PM +0200, Kory Maincent wrote:
> On Thu, 24 Oct 2024 15:52:23 +0100
> Simon Horman <horms@kernel.org> wrote:
>
> > On Wed, Oct 23, 2024 at 04:15:58PM +0200, Kory Maincent wrote:
> > > ETHTOOL_MSG_PHY_GET/GET_REPLY/NTF is missing in the ethtool message list.
> > > Add it to the ethool netlink documentation.
> > >
> > > Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
> > > ---
> > > Documentation/networking/ethtool-netlink.rst | 3 +++
> > > 1 file changed, 3 insertions(+)
> > >
> > > diff --git a/Documentation/networking/ethtool-netlink.rst
> > > b/Documentation/networking/ethtool-netlink.rst index
> > > 295563e91082..70ecc3821007 100644 ---
> > > a/Documentation/networking/ethtool-netlink.rst +++
> > > b/Documentation/networking/ethtool-netlink.rst @@ -236,6 +236,7 @@
> > > Userspace to kernel: ``ETHTOOL_MSG_MM_GET`` get MAC merge
> > > layer state ``ETHTOOL_MSG_MM_SET`` set MAC merge layer
> > > parameters ``ETHTOOL_MSG_MODULE_FW_FLASH_ACT`` flash transceiver module
> > > firmware
> > > + ``ETHTOOL_MSG_PHY_GET`` get Ethernet PHY information
> > > ===================================== =================================
> > >
> > > Kernel to userspace:
> > > @@ -283,6 +284,8 @@ Kernel to userspace:
> > > ``ETHTOOL_MSG_PLCA_NTF`` PLCA RS parameters
> > > ``ETHTOOL_MSG_MM_GET_REPLY`` MAC merge layer status
> > > ``ETHTOOL_MSG_MODULE_FW_FLASH_NTF`` transceiver module flash updates
> > > + ``ETHTOOL_MSG_PHY_GET_REPLY`` Ethernet PHY information
> > > + ``ETHTOOL_MSG_PHY_NTF`` Ethernet PHY information
> >
> > I wonder if ETHTOOL_MSG_PHY_NTF should be removed.
> > It doesn't seem to be used anywhere.
>
> We can't, as it is in the ethtool UAPI. Also I believe Maxime will use it on
> later patch series. Maxime, you confirm?
Ok, if it's in the UAPI then I suppose it needs to stay.
But could we differentiate in the documentation between
ETHTOOL_MSG_PHY_GET_REPLY and ETHTOOL_MSG_PHY_NTF?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH net-next] Documentation: networking: Add missing PHY_GET command in the message list
2024-10-24 15:28 ` Simon Horman
@ 2024-10-24 16:11 ` Maxime Chevallier
0 siblings, 0 replies; 5+ messages in thread
From: Maxime Chevallier @ 2024-10-24 16:11 UTC (permalink / raw)
To: Simon Horman
Cc: Kory Maincent, netdev, linux-doc, linux-kernel, thomas.petazzoni,
David S. Miller, Eric Dumazet, Jakub Kicinski, Paolo Abeni,
Jonathan Corbet
Hi Simon,
On Thu, 24 Oct 2024 16:28:16 +0100
Simon Horman <horms@kernel.org> wrote:
> On Thu, Oct 24, 2024 at 05:18:02PM +0200, Kory Maincent wrote:
> > On Thu, 24 Oct 2024 15:52:23 +0100
> > Simon Horman <horms@kernel.org> wrote:
> >
> > > On Wed, Oct 23, 2024 at 04:15:58PM +0200, Kory Maincent wrote:
> > > > ETHTOOL_MSG_PHY_GET/GET_REPLY/NTF is missing in the ethtool message list.
> > > > Add it to the ethool netlink documentation.
> > > >
> > > > Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
> > > > ---
> > > > Documentation/networking/ethtool-netlink.rst | 3 +++
> > > > 1 file changed, 3 insertions(+)
> > > >
> > > > diff --git a/Documentation/networking/ethtool-netlink.rst
> > > > b/Documentation/networking/ethtool-netlink.rst index
> > > > 295563e91082..70ecc3821007 100644 ---
> > > > a/Documentation/networking/ethtool-netlink.rst +++
> > > > b/Documentation/networking/ethtool-netlink.rst @@ -236,6 +236,7 @@
> > > > Userspace to kernel: ``ETHTOOL_MSG_MM_GET`` get MAC merge
> > > > layer state ``ETHTOOL_MSG_MM_SET`` set MAC merge layer
> > > > parameters ``ETHTOOL_MSG_MODULE_FW_FLASH_ACT`` flash transceiver module
> > > > firmware
> > > > + ``ETHTOOL_MSG_PHY_GET`` get Ethernet PHY information
> > > > ===================================== =================================
> > > >
> > > > Kernel to userspace:
> > > > @@ -283,6 +284,8 @@ Kernel to userspace:
> > > > ``ETHTOOL_MSG_PLCA_NTF`` PLCA RS parameters
> > > > ``ETHTOOL_MSG_MM_GET_REPLY`` MAC merge layer status
> > > > ``ETHTOOL_MSG_MODULE_FW_FLASH_NTF`` transceiver module flash updates
> > > > + ``ETHTOOL_MSG_PHY_GET_REPLY`` Ethernet PHY information
> > > > + ``ETHTOOL_MSG_PHY_NTF`` Ethernet PHY information
> > >
> > > I wonder if ETHTOOL_MSG_PHY_NTF should be removed.
> > > It doesn't seem to be used anywhere.
> >
> > We can't, as it is in the ethtool UAPI. Also I believe Maxime will use it on
> > later patch series. Maxime, you confirm?
>
> Ok, if it's in the UAPI then I suppose it needs to stay.
>
> But could we differentiate in the documentation between
> ETHTOOL_MSG_PHY_GET_REPLY and ETHTOOL_MSG_PHY_NTF?
Yeah it was a leftover from when I implemented that, however I do plan
on adding this notification though, so if it's OK for it to stay that's
perfect as it'll get used.
Then for the documentation, we can specify "Ethernet PHY information
change notification". This would trigger when the PHYs are appearing on
the topology.
Thanks,
Maxime
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2024-10-24 16:12 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-10-23 14:15 [PATCH net-next] Documentation: networking: Add missing PHY_GET command in the message list Kory Maincent
2024-10-24 14:52 ` Simon Horman
2024-10-24 15:18 ` Kory Maincent
2024-10-24 15:28 ` Simon Horman
2024-10-24 16:11 ` Maxime Chevallier
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).