linux-kernel - Re: [PATCH net-next v3] dsa: lan9303: Add 3 ethtool stats

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20221130185026.pxdv7daoiqliz7qq@skbuf>
Date:   Wed, 30 Nov 2022 20:50:26 +0200
From:   Vladimir Oltean <olteanv@...il.com>
To:     Jerry.Ray@...rochip.com
Cc:     kuba@...nel.org, andrew@...n.ch, f.fainelli@...il.com,
        davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v3] dsa: lan9303: Add 3 ethtool stats

On Wed, Nov 30, 2022 at 06:12:54PM +0000, Jerry.Ray@...rochip.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.