From: Greg KH <gregkh@linuxfoundation.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] io_uring: move read/write file prep state into actual opcode" failed to apply to 5.15-stable tree
Date: Tue, 12 Apr 2022 07:12:15 +0200 [thread overview]
Message-ID: <YlUKLyMirD242p1l@kroah.com> (raw)
In-Reply-To: <7bc5956c-46f1-9411-7ba7-6bfd92b7323c@kernel.dk>
On Mon, Apr 11, 2022 at 01:50:55PM -0600, Jens Axboe wrote:
> On 4/11/22 1:44 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>.
>
> For now, let's just drop this series otherwise marked for 5.15+ for
> 5.15-stable and 5.16-stable. It would require further backporting, and
> it isn't strictly necessary.
Ok, thanks for letting me know.
greg k-h
prev parent reply other threads:[~2022-04-12 5:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 7:44 FAILED: patch "[PATCH] io_uring: move read/write file prep state into actual opcode" failed to apply to 5.15-stable tree gregkh
2022-04-11 19:50 ` Jens Axboe
2022-04-12 5:12 ` Greg KH [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=YlUKLyMirD242p1l@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=axboe@kernel.dk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.