netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Kory Maincent <kory.maincent@bootlin.com>,
	Lukasz Majewski <lukma@denx.de>, Jonathan Corbet <corbet@lwn.net>,
	kernel@pengutronix.de, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, Russell King <linux@armlinux.org.uk>
Subject: Re: [PATCH net-next v2 1/1] Documentation: networking: add Twisted Pair Ethernet diagnostics at OSI Layer 1
Date: Fri, 4 Oct 2024 13:52:05 +0200	[thread overview]
Message-ID: <Zv_W5VDlTahegOZc@pengutronix.de> (raw)
In-Reply-To: <20241003095321.5a3c4e26@fedora.home>

Hi Maxime,

On Thu, Oct 03, 2024 at 09:53:21AM +0200, Maxime Chevallier wrote:
...
> > +  - **Wake-on**: Displays whether Wake-on-LAN is enabled (e.g., **Wake-on: d**
> > +    for disabled). Not used for layer 1 diagnostic.
> 
> (sorry for the long scroll down there) This whole section is more of a
> documentation on what ethtool reports rather than a troubleshooting
> guide. I'm all in for getting proper doc for this, but maybe we could
> move this in a dedicated page, that we would cross-link from that guide
> ?

Ack, I was not sure where to put it. I'll try to come up with ethtool
manual patches and drop for now everything no directly related with the
diagnostic.

> > +This list will evolve with future kernel versions, reflecting new features or
> > +refinements. Below are the current suggestions:
> 
> I'm not sure this TODO list has its place in this troubleshooting
> guide. I agree with the points you list, but this looks more like a
> roadmap for PHY stuff to improve. I don't really know where this list
> could go and if it's common to maintain this kind of "TODO list" in the
> kernel doc though. Maybe Andrew has an idea ?

Yea,  may be it will be enough to send it as separate mail for
discussion.

> Thanks for coming-up with such a detailed guide. I also have some "PHY
> bringup 101" ideas on the common errors faced by developers, and this is
> document would be the ideal place to maintain this crucial information.

Good idea. It will be good to have a list or guide on what options are expected
form from PHY driver and how to test them.

Regards,
Oleksij
-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2024-10-04 11:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-03  6:06 [PATCH net-next v2 1/1] Documentation: networking: add Twisted Pair Ethernet diagnostics at OSI Layer 1 Oleksij Rempel
2024-10-03  7:53 ` Maxime Chevallier
2024-10-04 11:52   ` Oleksij Rempel [this message]
2024-10-03 10:34 ` Divya.Koppera
     [not found] ` <CO1PR11MB477100FB112A842674009A1AE2712@CO1PR11MB4771.namprd11.prod.outlook.com>
2024-10-04 11:28   ` Oleksij Rempel

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=Zv_W5VDlTahegOZc@pengutronix.de \
    --to=o.rempel@pengutronix.de \
    --cc=andrew@lunn.ch \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=kory.maincent@bootlin.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=lukma@denx.de \
    --cc=maxime.chevallier@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh@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 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).