Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: stable@vger.kernel.org, Sunyi Shao <sunyishao@fb.com>,
	Mat Martineau <mathew.j.martineau@linux.intel.com>,
	Eric Dumazet <edumazet@google.com>,
	"David S . Miller" <davem@davemloft.net>
Subject: Re: FAILED: Patch "ipv6: weaken the v4mapped source check" failed to apply to 5.4-stable tree
Date: Mon, 29 Mar 2021 13:51:40 -0400	[thread overview]
Message-ID: <YGITrBHLOcm5X1ky@sashalap> (raw)
In-Reply-To: <20210329101957.4189475e@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

On Mon, Mar 29, 2021 at 10:19:57AM -0700, Jakub Kicinski wrote:
>On Mon, 29 Mar 2021 12:50:39 -0400 Sasha Levin wrote:
>> The patch below does not apply to the 5.4-stable tree.
>> If someone wants it applied there, or to any other stable or longterm
>> tree, then please email the backport, including the original git commit
>> id to <stable@vger.kernel.org>.
>
>> ------------------ original commit in Linus's tree ------------------
>>
>> From dcc32f4f183ab8479041b23a1525d48233df1d43 Mon Sep 17 00:00:00 2001
>> From: Jakub Kicinski <kuba@kernel.org>
>> Date: Wed, 17 Mar 2021 09:55:15 -0700
>> Subject: [PATCH] ipv6: weaken the v4mapped source check
>
>Hi Sasha! MPTCP did not exist in older trees, you'd just need to drop
>that chunk:
>
>$ git rm net/mptcp/subflow.c
>
>and the rest should apply cleanly. Would you mind trying that? Thanks!

Will do, thanks!

-- 
Thanks,
Sasha

      reply	other threads:[~2021-03-29 17:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29 16:50 FAILED: Patch "ipv6: weaken the v4mapped source check" failed to apply to 5.4-stable tree Sasha Levin
2021-03-29 17:19 ` Jakub Kicinski
2021-03-29 17:51   ` Sasha Levin [this message]

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=YGITrBHLOcm5X1ky@sashalap \
    --to=sashal@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=mathew.j.martineau@linux.intel.com \
    --cc=stable@vger.kernel.org \
    --cc=sunyishao@fb.com \
    /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