[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <715c5c81-9b0a-4182-a5a1-f5341ee79040@oracle.com>
Date: Thu, 1 Feb 2024 16:20:11 +0000
From: John Garry <john.g.garry@...cle.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Jiri Pirko <jiri@...nulli.us>, mcgrof@...nel.org, russ.weight@...ux.dev,
        gregkh@...uxfoundation.org, rafael@...nel.org, rostedt@...dmis.org,
        mhiramat@...nel.org, mathieu.desnoyers@...icios.com,
        davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
        keescook@...omium.org, masahiroy@...nel.org, nathan@...nel.org,
        nicolas@...sle.eu, linux-kernel@...r.kernel.org,
        linux-trace-kernel@...r.kernel.org, netdev@...r.kernel.org,
        linux-kbuild@...r.kernel.org
Subject: Re: [PATCH RFC 3/4] net: ethtool: Use uts_release
On 01/02/2024 16:09, Jakub Kicinski wrote:
> On Thu, 1 Feb 2024 14:20:23 +0100 Jiri Pirko wrote:
>>> BTW, I assume that changes like this are also ok:
>>>
>>> --------8<---------
>>>
>>>    net: team: Don't bother filling in ethtool driver version
> 
> Yup, just to be clear - you can send this independently from the series,
Sure, and I think rocker and staging/octeon also have this unnecessary 
code also.
> tag is as
> 
>   [PATCH net-next]
ah, yes
> 
> we'll take it via the networking tree.
Thanks. I assume Greg - the staging maintainer - would take the octeon 
patch.
> I'm not sure which tree the other
> patches will go thru..
I think that the best thing to do is get a minimal set in for 6.9 and 
then merge the rest in the next cycle. I've got about 22 patches in 
total now, but I think that there will be more. We'll see who can pick 
up the first set when I send it officially.
Thanks,
John
Powered by blists - more mailing lists