public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Paolo Valente <paolo.valente@linaro.org>
Cc: stable@vger.kernel.org, Chris Evich <cevich@redhat.com>
Subject: Re: block, bfq: port of a series of fix commits to 5.4 and 5.5
Date: Fri, 6 Mar 2020 08:33:43 -0500	[thread overview]
Message-ID: <20200306133343.GP21491@sasha-vm> (raw)
In-Reply-To: <543B99A1-B872-4F06-9A0F-EFFB9CAD5E14@linaro.org>

Hi Paolo,

On Thu, Mar 05, 2020 at 07:49:29AM +0100, Paolo Valente wrote:
>Hi,
>Fedora requested the following fix commits, currently available in
>5.6-rc4, to be ported to 5.4 and 5.5 [1]:
>db37a34c563b block, bfq: get a ref to a group when adding it to a service tree

I took this one.

>4d8340d0d4d9 block, bfq: remove ifdefs from around gets/puts of bfq groups

But not this one, it looks like a cleanup that isn't needed by the
following patches.

>33a16a980468 block, bfq: extend incomplete name of field on_st

Same as above.

>ecedd3d7e199 block, bfq: get extra ref to prevent a queue from being freed during a group move

I took this one.

>32c59e3a9a5a block, bfq: do not insert oom queue into position tree

And this one.

>f718b093277d block, bfq: do not plug I/O for bfq_queues with no proc refs

This patch seems to be already in.

>This is the first time I submit something for stable branches, I hope
>I did everything right (I'm following option 2 in [2]).

You did, thank you :)

-- 
Thanks,
Sasha

      parent reply	other threads:[~2020-03-06 13:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05  6:49 block, bfq: port of a series of fix commits to 5.4 and 5.5 Paolo Valente
2020-03-05 12:35 ` Thomas Backlund
2020-03-05 16:00   ` Paolo Valente
2020-03-06 13:33 ` Sasha Levin [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=20200306133343.GP21491@sasha-vm \
    --to=sashal@kernel.org \
    --cc=cevich@redhat.com \
    --cc=paolo.valente@linaro.org \
    --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