All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jan Kara <jack@suse.cz>
Cc: stable@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
	Paolo Valente <paolo.valente@linaro.org>,
	linux-block@vger.kernel.org
Subject: Re: [PATCH 0/6] bfq: cgroup fixes for 5.4 stable
Date: Tue, 7 Jun 2022 11:57:45 +0200	[thread overview]
Message-ID: <Yp8hGR3L1G3ZMbau@kroah.com> (raw)
In-Reply-To: <20220607091209.24033-1-jack@suse.cz>

On Tue, Jun 07, 2022 at 11:15:08AM +0200, Jan Kara wrote:
> Hello,
> 
> In this series are BFQ upstream fixes that didn't apply to 5.4 stable tree
> cleanly and needed some massaging before they apply. The result did pass
> some cgroup testing with bfq and the backport is based on the one we have
> in our SLES kernel so I'm reasonably confident things are fine.

All now queued up, thanks for the backports!

greg k-h

      parent reply	other threads:[~2022-06-07  9:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07  9:15 [PATCH 0/6] bfq: cgroup fixes for 5.4 stable Jan Kara
2022-06-07  9:15 ` [PATCH 1/6] bfq: Avoid merging queues with different parents Jan Kara
2022-06-07  9:15 ` [PATCH 2/6] bfq: Drop pointless unlock-lock pair Jan Kara
2022-06-07  9:15 ` [PATCH 3/6] bfq: Remove pointless bfq_init_rq() calls Jan Kara
2022-06-07  9:15 ` [PATCH 4/6] bfq: Get rid of __bio_blkcg() usage Jan Kara
2022-06-07  9:15 ` [PATCH 5/6] bfq: Make sure bfqg for which we are queueing requests is online Jan Kara
2022-06-07  9:15 ` [PATCH 6/6] block: fix bio_clone_blkg_association() to associate with proper blkcg_gq Jan Kara
2022-06-07  9:57 ` 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=Yp8hGR3L1G3ZMbau@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=axboe@kernel.dk \
    --cc=jack@suse.cz \
    --cc=linux-block@vger.kernel.org \
    --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 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.