[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <60508ed0-dfe0-5981-6358-f87c860ccc8c@huawei.com>
Date: Tue, 18 Apr 2023 20:53:32 +0800
From: "Ziyang Xuan (William)" <william.xuanziyang@...wei.com>
To: Greg KH <gregkh@...uxfoundation.org>
CC: <stable@...r.kernel.org>, <davem@...emloft.net>,
<kuznet@....inr.ac.ru>, <yoshfuji@...ux-ipv6.org>,
<kuba@...nel.org>, <kuniyu@...zon.com>, <netdev@...r.kernel.org>
Subject: Re: [PATCH 5.10 1/5] udp: Call inet6_destroy_sock() in
setsockopt(IPV6_ADDRFORM).
> On Tue, Apr 18, 2023 at 12:21:21PM +0200, Greg KH wrote:
>> On Tue, Apr 04, 2023 at 05:24:28PM +0800, Ziyang Xuan wrote:
>>> From: Kuniyuki Iwashima <kuniyu@...zon.com>
>>>
>>> commit 21985f43376cee092702d6cb963ff97a9d2ede68 upstream.
>>
>> Why is this only relevant for 5.10.y? What about 5.15.y?
>>
>> For obvious reasons, we can not take patches only for older branches as
>> that would cause people to have regressions when moving to newer kernel
>> releases. So can you please fix this up by sending a 5.15.y series, and
>> this 5.10.y series again, and we can queue them all up at the same time?
>
> Also a 6.1.y series to be complete.
>
4.14.y, 4.19.y, 5.4.y, 5.10.y, 5.15.y and 6.1.y are all involved.
Can I send series for them all together?
William Xuan
> thanks,
>
> greg k-h
> .
>
Powered by blists - more mailing lists