From: Greg KH <gregkh@linuxfoundation.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: cyphar@cyphar.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] io_uring: correct check for O_TMPFILE" failed to apply to 5.15-stable tree
Date: Sat, 12 Aug 2023 18:28:53 +0200 [thread overview]
Message-ID: <2023081246-pledge-record-7c35@gregkh> (raw)
In-Reply-To: <b2efb91d-6b4b-40fa-bbc9-9511d0a70f27@kernel.dk>
On Sat, Aug 12, 2023 at 07:33:03AM -0600, Jens Axboe wrote:
> On 8/12/23 7:20 AM, Jens Axboe wrote:
> > On 8/12/23 12:02 AM, gregkh@linuxfoundation.org wrote:
> >>
> >> The patch below does not apply to the 5.15-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>.
> >>
> >> To reproduce the conflict and resubmit, you may use the following commands:
> >>
> >> git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-5.15.y
> >> git checkout FETCH_HEAD
> >> git cherry-pick -x 72dbde0f2afbe4af8e8595a89c650ae6b9d9c36f
> >> # <resolve conflicts, build, test, etc.>
> >> git commit -s
> >> git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2023081258-sturdy-retying-2572@gregkh' --subject-prefix 'PATCH 5.15.y' HEAD^..
> >
> > Here's one for 5.15-stable.
>
> Oh, and the 5.15-stable one also applies to 5.10-stable. 5.10-stable
> needs it as well, would be great if you could queue it up there as well.
All now queued up, thanks!
greg k-h
next prev parent reply other threads:[~2023-08-12 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 6:02 FAILED: patch "[PATCH] io_uring: correct check for O_TMPFILE" failed to apply to 5.15-stable tree gregkh
2023-08-12 13:20 ` Jens Axboe
2023-08-12 13:33 ` Jens Axboe
2023-08-12 16:28 ` Greg KH [this message]
2023-08-12 21:52 ` Jens Axboe
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=2023081246-pledge-record-7c35@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=axboe@kernel.dk \
--cc=cyphar@cyphar.com \
--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