All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: zeba.hrvoje@gmail.com, stable@vger.kernel.org,
	Sasha Levin <sashal@kernel.org>
Subject: Re: FAILED: patch "[PATCH] io_uring: fix up O_NONBLOCK handling for sockets" failed to apply to 5.3-stable tree
Date: Sun, 27 Oct 2019 14:39:06 -0600	[thread overview]
Message-ID: <25f998ae-e6d4-9e62-3b3d-996cd92e80cb@kernel.dk> (raw)
In-Reply-To: <20191027202633.GA2608793@kroah.com>

On 10/27/19 2:26 PM, Greg KH wrote:
> On Sun, Oct 27, 2019 at 02:22:06PM -0600, Jens Axboe wrote:
>> On 10/27/19 2:00 PM, Greg KH wrote:
>>> On Sun, Oct 27, 2019 at 12:58:14PM -0600, Jens Axboe wrote:
>>>> On 10/27/19 9:53 AM, gregkh@linuxfoundation.org wrote:
>>>>>
>>>>> The patch below does not apply to the 5.3-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 can fix this up, but I probably need to see Sasha's queue first for
>>>> the io_uring patches. I need to base it against that.
>>>
>>> Ok, wait for the next 5.3.y release in a few days and send stuff off of
>>> that if you can.
>>
>> Is there no "current" or similar tree to work of off? Would be a shame
>> to miss the next one, especially since the newer fixes are already in.
> 
> I'm about to push out the -rcs right now.  You can base off of that and
> send me the patch and I'll add it, or just wait a few days, either is
> fine.

Sounds good, thanks Greg.

-- 
Jens Axboe


  reply	other threads:[~2019-10-27 20:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-27 15:53 FAILED: patch "[PATCH] io_uring: fix up O_NONBLOCK handling for sockets" failed to apply to 5.3-stable tree gregkh
2019-10-27 18:58 ` Jens Axboe
2019-10-27 20:00   ` Greg KH
2019-10-27 20:22     ` Jens Axboe
2019-10-27 20:26       ` Greg KH
2019-10-27 20:39         ` Jens Axboe [this message]
2019-10-28  8:26           ` Sasha Levin
2019-10-28 15:21             ` 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=25f998ae-e6d4-9e62-3b3d-996cd92e80cb@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=gregkh@linuxfoundation.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=zeba.hrvoje@gmail.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.