[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4afe24a1-9281-41ef-98ff-7d32872afe66@gmail.com>
Date: Tue, 16 Jan 2024 10:43:03 -0800
From: Florian Fainelli <f.fainelli@...il.com>
To: Andy Gospodarek <andrew.gospodarek@...adcom.com>,
Andrew Lunn <andrew@...n.ch>
Cc: John Fastabend <john.fastabend@...il.com>,
Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
netdev-driver-reviewers@...r.kernel.org
Subject: Re: [ANN] netdev call - Jan 16th
On 1/16/24 08:12, Andy Gospodarek wrote:
> On Tue, Jan 16, 2024 at 05:10:31PM +0100, Andrew Lunn wrote:
>>> Thanks, John.
>>>
>>> This one is a bit odd what happened is that by the time this problem was
>>> reported (on an older kernel), the code changed out from underneath.
>>
>> Hi Andy
>>
>> Talk to Florian
>>
>> He has dealt with Fixes like this in the past. It generally works out
>> fine so long as you are explicit about what is going on, in comments
>> under the ---. That, plus correctly marking what kernel version the
>> patch is for.
>>
>> Andrew
>
> Will do! I know where to find him!
Hi there! It looks like doing a "targeted" set of fixes for pre-6.6
kernels is appropriate so you would just want to submit them with a
[PATCH stable X.Y] subject to clearly denote which stable branch they
apply against, and have a cover letter that explains why.
--
Florian
Powered by blists - more mailing lists