MPTCP Linux Development
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>,
	Mat Martineau <mathew.j.martineau@linux.intel.com>
Cc: MPTCP Upstream <mptcp@lists.linux.dev>
Subject: Re: Patch "mptcp: strict local address ID selection" has been added to the 5.17-stable tree
Date: Mon, 23 May 2022 19:41:08 +0200	[thread overview]
Message-ID: <fc5e28d40fb054e586f84bc7b85b64b3985aa016.camel@redhat.com> (raw)
In-Reply-To: <4668b747-35fa-d6b0-8390-24c0f8f62a71@tessares.net>

On Mon, 2022-05-23 at 17:33 +0200, Matthieu Baerts wrote:
> Hi Mat, Paolo,
> 
> (- stable list and netdev maintainers, + mptcp list)
> 
> On 23/05/2022 05:06, Sasha Levin wrote:
> > This is a note to let you know that I've just added the patch titled
> > 
> >     mptcp: strict local address ID selection
> > 
> > to the 5.17-stable tree which can be found at:
> >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > 
> > The filename of the patch is:
> >      mptcp-strict-local-address-id-selection.patch
> > and it can be found in the queue-5.17 subdirectory.
> > 
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> 
> 
> Do we want the patch below to be backported to stable?
> 
> It think it is slightly changing the behaviour and we might not want it
> there, no?

I don't have hard-preferences, but I *think* we are better-off with
this patch and the csum-one in without any additional effort, than to
craft csum specifically for stable (and delay it). 

Cheers,

Paolo


      parent reply	other threads:[~2022-05-23 17:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220523030625.741995-1-sashal@kernel.org>
2022-05-23 15:33 ` Patch "mptcp: strict local address ID selection" has been added to the 5.17-stable tree Matthieu Baerts
2022-05-23 15:40   ` Matthieu Baerts
2022-05-23 18:20     ` Mat Martineau
2022-05-23 17:41   ` Paolo Abeni [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=fc5e28d40fb054e586f84bc7b85b64b3985aa016.camel@redhat.com \
    --to=pabeni@redhat.com \
    --cc=mathew.j.martineau@linux.intel.com \
    --cc=matthieu.baerts@tessares.net \
    --cc=mptcp@lists.linux.dev \
    /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