linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Larkin Lowrey <llowrey@nuclearwinter.com>,
	Song Liu <song@kernel.org>,
	linux-raid <linux-raid@vger.kernel.org>,
	Wilson Jonathan <i400sjon@gmail.com>,
	Roger Heflin <rogerheflin@gmail.com>
Subject: Re: [PATCH] block: check more requests for multiple_queues in blk_attempt_plug_merge
Date: Wed, 30 Mar 2022 09:39:42 -0600	[thread overview]
Message-ID: <46cb9609-ffb5-74aa-e4a1-598c86be9db9@kernel.dk> (raw)
In-Reply-To: <YkR0gvkIOONNYo/d@kroah.com>

On 3/30/22 9:17 AM, Greg Kroah-Hartman wrote:
> On Wed, Mar 30, 2022 at 08:49:07AM -0600, Jens Axboe wrote:
>> On 3/30/22 8:39 AM, Larkin Lowrey wrote:
>>> Thank you for investigating and resolving this issue. Your effort is
>>> very much appreciated.
>>>
>>> I am interested in when this patch will end up in a release. Is it
>>> going to make it into a 5.17.x release or will it not come until 5.18?
>>
>> The two patches are merged for 5.18, and I just checked and they apply
>> directly to 5.17 as well.
>>
>> Greg, care to queue up the two attached patches for 5.17-stable?
> 
> Now queued up, but shouldn't they also work for 5.16?  They don't apply
> there, but the Fixes: tag says it should.

Yes, they should go to 5.16-stable as well. Song, do you have time to
port and test on 5.16?

-- 
Jens Axboe


  reply	other threads:[~2022-03-30 15:39 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09  6:42 [PATCH] block: check more requests for multiple_queues in blk_attempt_plug_merge Song Liu
2022-03-10  6:48 ` Christoph Hellwig
2022-03-10  7:23   ` Song Liu
2022-03-10 22:10     ` Song Liu
2022-03-10 22:12       ` Song Liu
2022-03-10 22:15 ` Jens Axboe
2022-03-10 22:37   ` Song Liu
2022-03-10 23:02     ` Jens Axboe
2022-03-10 23:33       ` Song Liu
2022-03-11  0:07         ` Jens Axboe
2022-03-11  0:31           ` Song Liu
2022-03-11  0:36             ` Jens Axboe
2022-03-11  0:38               ` Jens Axboe
2022-03-11  1:14               ` Ming Lei
2022-03-11  1:21                 ` Jens Axboe
2022-03-11  1:32                   ` Ming Lei
2022-03-11  1:35                     ` Jens Axboe
2022-03-11  8:09                       ` Wols Lists
2022-03-11 14:16           ` Jens Axboe
2022-03-11 16:59             ` Song Liu
2022-03-11 21:41               ` Paul Menzel
2022-03-11 22:40                 ` Song Liu
2022-03-30 14:39               ` Larkin Lowrey
2022-03-30 14:49                 ` Jens Axboe
2022-03-30 15:17                   ` Greg Kroah-Hartman
2022-03-30 15:39                     ` Jens Axboe [this message]
     [not found]                       ` <CAAMCDefQQqwsLNmBjArTipLDnKzW2nQBW4MTHajrjKS4oi=JFg@mail.gmail.com>
2022-03-30 18:50                         ` Song Liu
2022-03-30 19:01                           ` Jens Axboe
2022-03-31  6:14                             ` Greg Kroah-Hartman
2022-03-11 11:30     ` Wilson Jonathan
2022-03-11 15:58       ` Wols Lists

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=46cb9609-ffb5-74aa-e4a1-598c86be9db9@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=gregkh@linuxfoundation.org \
    --cc=i400sjon@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=llowrey@nuclearwinter.com \
    --cc=rogerheflin@gmail.com \
    --cc=song@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;
as well as URLs for NNTP newsgroup(s).