From: Florian Fainelli <f.fainelli@gmail.com>
To: Andy Gospodarek <andrew.gospodarek@broadcom.com>,
Andrew Lunn <andrew@lunn.ch>
Cc: John Fastabend <john.fastabend@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, netdev-driver-reviewers@vger.kernel.org
Subject: Re: [ANN] netdev call - Jan 16th
Date: Tue, 16 Jan 2024 10:43:03 -0800 [thread overview]
Message-ID: <4afe24a1-9281-41ef-98ff-7d32872afe66@gmail.com> (raw)
In-Reply-To: <Zaaq6kh1IgDdy9SW@C02YVCJELVCG>
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
next prev parent reply other threads:[~2024-01-16 18:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 1:54 [ANN] netdev call - Jan 16th Jakub Kicinski
2024-01-16 15:19 ` Andy Gospodarek
2024-01-16 15:29 ` John Fastabend
2024-01-16 16:04 ` Andy Gospodarek
2024-01-16 16:10 ` Andrew Lunn
2024-01-16 16:12 ` Andy Gospodarek
2024-01-16 18:43 ` Florian Fainelli [this message]
2024-01-17 22:26 ` Jakub Kicinski
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=4afe24a1-9281-41ef-98ff-7d32872afe66@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=andrew@lunn.ch \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev-driver-reviewers@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).