From: Jakub Kicinski <kuba@kernel.org>
To: <Jerry.Ray@microchip.com>
Cc: <olteanv@gmail.com>, <andrew@lunn.ch>, <f.fainelli@gmail.com>,
<davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v4] dsa: lan9303: Add 3 ethtool stats
Date: Thu, 1 Dec 2022 08:45:59 -0800 [thread overview]
Message-ID: <20221201084559.5ac2f1e6@kernel.org> (raw)
In-Reply-To: <MWHPR11MB1693DA619CAC5AA135B47424EF149@MWHPR11MB1693.namprd11.prod.outlook.com>
On Thu, 1 Dec 2022 16:42:10 +0000 Jerry.Ray@microchip.com wrote:
> get_stats64 will require PHYLINK.
Huh? I'm guessing you're referring to some patches you have queued
already and don't want to rebase across? Or some project planning?
Otherwise I don't see a connection :S
next prev parent reply other threads:[~2022-12-01 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 20:08 [PATCH net-next v4] dsa: lan9303: Add 3 ethtool stats Jerry Ray
2022-11-30 20:56 ` Vladimir Oltean
2022-12-01 16:42 ` Jerry.Ray
2022-12-01 16:45 ` Jakub Kicinski [this message]
2022-12-02 15:22 ` Jerry.Ray
2022-12-02 19:36 ` Jakub Kicinski
2022-12-06 19:55 ` Vladimir Oltean
2022-12-06 22:38 ` Jerry.Ray
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=20221201084559.5ac2f1e6@kernel.org \
--to=kuba@kernel.org \
--cc=Jerry.Ray@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--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).