netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
	Florian Fainelli <f.fainelli@gmail.com>,
	Michael Chan <michael.chan@broadcom.com>,
	Andrew Lunn <andrew@lunn.ch>,
	corbet@lwn.net, hkallweit1@gmail.com, linux@armlinux.org.uk,
	huangguangbin2@huawei.com, chenhao288@hisilicon.com,
	moshet@nvidia.com, linux@rempel-privat.de,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next v4] ethtool: linkstate: add a statistic for PHY down events
Date: Wed, 2 Nov 2022 09:31:33 -0700	[thread overview]
Message-ID: <20221102093133.4000add1@kernel.org> (raw)
In-Reply-To: <20221102035704.110304-1-kuba@kernel.org>

On Tue,  1 Nov 2022 20:57:04 -0700 Jakub Kicinski wrote:
> +	 * This statistic counts when PHY _actually_ went down, or lost link.
> +	 */

Please ignore, I just realized I forgot to commit the change:

diff --git a/include/linux/ethtool.h b/include/linux/ethtool.h
index fa8e0d52dd30..15c0134ae938 100644
--- a/include/linux/ethtool.h
+++ b/include/linux/ethtool.h
@@ -132,6 +132,9 @@ struct ethtool_link_ext_stats {
         * actually take the physical link down, not to mention NC-SI which,
         * if present, keeps the link up regardless of host state.
         * This statistic counts when PHY _actually_ went down, or lost link.
+        *
+        * Note that we need u64 for ethtool_stats_init() and comparisons
+        * to ETHTOOL_STAT_NOT_SET, only u32 is exposed to the user.
         */
        u64 link_down_events;
 };

      reply	other threads:[~2022-11-02 16:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02  3:57 [PATCH net-next v4] ethtool: linkstate: add a statistic for PHY down events Jakub Kicinski
2022-11-02 16:31 ` Jakub Kicinski [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=20221102093133.4000add1@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=chenhao288@hisilicon.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=huangguangbin2@huawei.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linux@rempel-privat.de \
    --cc=michael.chan@broadcom.com \
    --cc=moshet@nvidia.com \
    --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 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).