From: Greg KH <gregkh@linuxfoundation.org>
To: Ziyang Xuan <william.xuanziyang@huawei.com>
Cc: stable@vger.kernel.org, davem@davemloft.net,
kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org, kuba@kernel.org,
kuniyu@amazon.com, netdev@vger.kernel.org
Subject: Re: [PATCH 5.10 1/5] udp: Call inet6_destroy_sock() in setsockopt(IPV6_ADDRFORM).
Date: Tue, 18 Apr 2023 12:21:55 +0200 [thread overview]
Message-ID: <2023041845-resize-elude-7fb6@gregkh> (raw)
In-Reply-To: <2023041820-storable-trimester-e98d@gregkh>
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@amazon.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.
thanks,
greg k-h
next prev parent reply other threads:[~2023-04-18 10:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 9:24 [PATCH 5.10 0/5] Backport complete patchset for call inet6_destroy_sock() in IPv6 sk->sk_destruct() Ziyang Xuan
2023-04-04 9:24 ` [PATCH 5.10 1/5] udp: Call inet6_destroy_sock() in setsockopt(IPV6_ADDRFORM) Ziyang Xuan
2023-04-18 10:21 ` Greg KH
2023-04-18 10:21 ` Greg KH [this message]
2023-04-18 12:53 ` Ziyang Xuan (William)
2023-04-18 12:57 ` Greg KH
2023-04-04 9:24 ` [PATCH 5.10 2/5] tcp/udp: Call inet6_destroy_sock() in IPv6 sk->sk_destruct() Ziyang Xuan
2023-04-04 9:24 ` [PATCH 5.10 3/5] inet6: Remove inet6_destroy_sock() in sk->sk_prot->destroy() Ziyang Xuan
2023-04-04 9:25 ` [PATCH 5.10 4/5] dccp: Call inet6_destroy_sock() via sk->sk_destruct() Ziyang Xuan
2023-04-04 9:25 ` [PATCH 5.10 5/5] sctp: " Ziyang Xuan
-- strict thread matches above, loose matches on Subject: below --
2023-04-20 3:23 [PATCH 5.10 0/5] inet6: Backport complete patchset for inet6_destroy_sock() call modification Ziyang Xuan
2023-04-20 3:23 ` [PATCH 5.10 1/5] udp: Call inet6_destroy_sock() in setsockopt(IPV6_ADDRFORM) Ziyang Xuan
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=2023041845-resize-elude-7fb6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=william.xuanziyang@huawei.com \
--cc=yoshfuji@linux-ipv6.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).