All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: xiaoguang.wang@linux.alibaba.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] io_uring: add memory barrier to synchronize io_kiocb's result" failed to apply to 5.7-stable tree
Date: Mon, 22 Jun 2020 20:19:28 +0200	[thread overview]
Message-ID: <20200622181928.GA2099850@kroah.com> (raw)
In-Reply-To: <68388f8d-f427-91ac-f503-6857ed47a75d@kernel.dk>

On Mon, Jun 22, 2020 at 12:12:50PM -0600, Jens Axboe wrote:
> On 6/22/20 12:09 PM, Greg KH wrote:
> > On Mon, Jun 22, 2020 at 12:02:26PM -0600, Jens Axboe wrote:
> >> On 6/22/20 11:48 AM, gregkh@linuxfoundation.org wrote:
> >>>
> >>> The patch below does not apply to the 5.7-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>.
> >>
> >> I took a look at the queue, and here's this one and the next two you
> >> reported that didn't apply.
> >>
> >> There's also a few more, I grabbed them as well. So could you just
> >> queue up these 6 for the next 5.7-stable? Thanks!
> > 
> > I will be glad to, thanks, but what is the git commit ids of them in
> > Linus's tree?  I need to put that in the changelog body...
> 
> Here they are again with that added.

That worked great, thanks, all now queued up!

greg k-h

      reply	other threads:[~2020-06-22 18:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22 17:48 FAILED: patch "[PATCH] io_uring: add memory barrier to synchronize io_kiocb's result" failed to apply to 5.7-stable tree gregkh
2020-06-22 18:02 ` Jens Axboe
2020-06-22 18:09   ` Greg KH
2020-06-22 18:12     ` Jens Axboe
2020-06-22 18:19       ` 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=20200622181928.GA2099850@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=axboe@kernel.dk \
    --cc=stable@vger.kernel.org \
    --cc=xiaoguang.wang@linux.alibaba.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 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.