public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: stable@vger.kernel.org, MPTCP Upstream <mptcp@lists.linux.dev>,
	Mat Martineau <martineau@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1.y] selftests: mptcp: join: validate event numbers
Date: Thu, 5 Sep 2024 11:36:19 +0200	[thread overview]
Message-ID: <2024090541-bride-marbled-f248@gregkh> (raw)
In-Reply-To: <2024090556-skewed-factoid-250c@gregkh>

On Thu, Sep 05, 2024 at 11:33:46AM +0200, Greg KH wrote:
> On Wed, Sep 04, 2024 at 05:20:59PM +0200, Matthieu Baerts wrote:
> > Hi Greg,
> > 
> > On 04/09/2024 16:38, Greg KH wrote:
> > > On Wed, Sep 04, 2024 at 01:13:39PM +0200, Matthieu Baerts (NGI0) wrote:
> > >> commit 20ccc7c5f7a3aa48092441a4b182f9f40418392e upstream.
> > >>
> > > 
> > > This did not apply either.
> > > 
> > > I think I've gone through all of the 6.1 patches now.  If I've missed
> > > anything, please let me know.
> > It looks like there are some conflicts with the patches Sasha recently
> > added:
> > 
> > queue-6.1/selftests-mptcp-add-explicit-test-case-for-remove-re.patch
> > queue-6.1/selftests-mptcp-join-check-re-adding-init-endp-with-.patch
> > queue-6.1/selftests-mptcp-join-check-re-using-id-of-unused-add.patch
> > 
> > >From commit 0d8d8d5bcef1 ("Fixes for 6.1") from the stable-queue tree:
> > 
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=0d8d8d5bcef1
> > 
> > I have also added these patches -- we can see patches with almost the
> > same name -- but I adapted them to the v6.1 kernel: it was possible to
> > apply them without conflicts, but they were causing issues because they
> > were calling functions that are not available in v6.1, or taking
> > different parameters.
> > 
> > Do you mind removing the ones from Sasha please? I hope that will not
> > cause any issues. After that, the two patches you had errors with should
> > apply without conflicts:
> 
> Ok, I've now dropped them, that actually fixes an error I was seeing
> where we had duplicated patches in the tree.
> 
> >  - selftests: mptcp: join: validate event numbers
> >  - selftests: mptcp: join: check re-re-adding ID 0 signal
> 
> I'll go add these now, thanks!

I just tried, and they still fail to apply.  How about we wait for this
next 6.1.y release to happen and then you rebase and see what I messed
up and send me the remaining ones as this is getting confusing on my
end...

thanks,

greg k-h

  reply	other threads:[~2024-09-05  9:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-30 10:28 FAILED: patch "[PATCH] selftests: mptcp: join: validate event numbers" failed to apply to 6.1-stable tree gregkh
2024-09-04 11:13 ` [PATCH 6.1.y] selftests: mptcp: join: validate event numbers Matthieu Baerts (NGI0)
2024-09-04 14:38   ` Greg KH
2024-09-04 15:20     ` Matthieu Baerts
2024-09-05  9:33       ` Greg KH
2024-09-05  9:36         ` Greg KH [this message]
2024-09-05  9:42           ` Matthieu Baerts
2024-09-05 10:10             ` Greg KH
2024-09-05 10:13               ` Matthieu Baerts
2024-09-05 14:43                 ` [PATCH 6.1.y 0/3] selftests: mptcp: fix backport issues Matthieu Baerts (NGI0)
2024-09-08 14:03                   ` Greg KH
2024-09-05 14:43                 ` [PATCH 6.1.y 1/3] " Matthieu Baerts (NGI0)
2024-09-05 14:43                 ` [PATCH 6.1.y 2/3] selftests: mptcp: join: validate event numbers Matthieu Baerts (NGI0)
2024-09-05 14:43                 ` [PATCH 6.1.y 3/3] selftests: mptcp: join: check re-re-adding ID 0 signal Matthieu Baerts (NGI0)

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=2024090541-bride-marbled-f248@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=martineau@kernel.org \
    --cc=matttbe@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=pabeni@redhat.com \
    --cc=sashal@kernel.org \
    --cc=stable@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