From: Vladimir Oltean <olteanv@gmail.com>
To: Jerry.Ray@microchip.com
Cc: kuba@kernel.org, andrew@lunn.ch, f.fainelli@gmail.com,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3] dsa: lan9303: Add 3 ethtool stats
Date: Wed, 30 Nov 2022 20:50:26 +0200 [thread overview]
Message-ID: <20221130185026.pxdv7daoiqliz7qq@skbuf> (raw)
In-Reply-To: <MWHPR11MB1693909B5E06A7791F0FD079EF159@MWHPR11MB1693.namprd11.prod.outlook.com>
On Wed, Nov 30, 2022 at 06:12:54PM +0000, Jerry.Ray@microchip.com wrote:
> Won't be able to get to stats64 this cycle. Looking to migrate to phylink
> first. This is a pretty old driver.
>
> Understand you don't know me - yet.
It would be good if you first prepared a bug fix patch for the existing
kernel stack memory leakage, and submit that to the net.git tree.
The net.git is merged back into net-next.git every ~Thursday, and
generally speaking, either you wait for bug fixes to land back into
net-next before you submit new net-next material in the same areas,
or the netdev and linux-next maintainers will have to resolve the merge
conflict between trees manually. Not a huge deal, but it is kind of a
nuisance for backports (to not be able to linearize a series of cherry
picks) and all in all, it's best to organize your work such that you
don't conflict with yourself.
next prev parent reply other threads:[~2022-11-30 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 20:55 [PATCH net-next v3] dsa: lan9303: Add 3 ethtool stats Jerry Ray
2022-11-28 21:05 ` Vladimir Oltean
2022-11-30 15:57 ` Jerry.Ray
2022-11-30 16:00 ` Andrew Lunn
2022-11-28 23:21 ` Jakub Kicinski
2022-11-30 15:51 ` Jerry.Ray
2022-11-30 16:52 ` Jakub Kicinski
2022-11-30 18:12 ` Jerry.Ray
2022-11-30 18:50 ` Vladimir Oltean [this message]
2022-12-01 15:56 ` 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=20221130185026.pxdv7daoiqliz7qq@skbuf \
--to=olteanv@gmail.com \
--cc=Jerry.Ray@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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