From: Greg KH <gregkh@linuxfoundation.org>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: axboe@kernel.dk, stable@vger.kernel.org,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
yi.zhang@hawei.com, "yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH 5.10 2/3] blk-wbt: call rq_qos_add() after wb_normal is initialized
Date: Thu, 27 Oct 2022 13:49:06 +0200 [thread overview]
Message-ID: <Y1pwMhBTym5CYH9q@kroah.com> (raw)
In-Reply-To: <fa4a2aed-4a9e-abfa-6fcf-d402ec9a1647@huaweicloud.com>
On Thu, Oct 27, 2022 at 07:28:26PM +0800, Yu Kuai wrote:
> Hi,
>
> 在 2022/10/27 0:47, Greg KH 写道:
> > On Tue, Oct 18, 2022 at 09:43:25AM +0800, Yu Kuai wrote:
> > > From: Yu Kuai <yukuai3@huawei.com>
> > >
> > > commit 8c5035dfbb9475b67c82b3fdb7351236525bf52b upstream.
> >
> > I need a 5.15 version of this, and the 3/3 patch in order to be able to
> > apply the 5.10.y version.
> >
> > Can you please send that, and then resend the remaining patches here for
> > 5.10.y?
>
> Yes, I can do that. By the way, just to confirm:
>
> I already saw that patch 2,3 is queued:
>
> [PATCH 5.15 122/530] blk-wbt: call rq_qos_add() after wb_normal is
> initialized
> [PATCH 5.15 519/530] blk-wbt: fix that rwb->wc is always set to 1 in
> wbt_init()
>
> Do I still need to send a 5.15 version?
Not if it is already in the tree, no.
thanks,
greg k-h
next prev parent reply other threads:[~2022-10-27 11:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 1:43 [PATCH 5.10 0/3] wbt stable patches Yu Kuai
2022-10-18 1:43 ` [PATCH 5.10 1/3] block: wbt: Remove unnecessary invoking of wbt_update_limits in wbt_init Yu Kuai
2022-10-18 1:43 ` [PATCH 5.10 2/3] blk-wbt: call rq_qos_add() after wb_normal is initialized Yu Kuai
2022-10-26 16:47 ` Greg KH
2022-10-27 11:28 ` Yu Kuai
2022-10-27 11:49 ` Greg KH [this message]
2022-10-18 1:43 ` [PATCH 5.10 3/3] blk-wbt: fix that 'rwb->wc' is always set to 1 in wbt_init() Yu Kuai
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=Y1pwMhBTym5CYH9q@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=yi.zhang@hawei.com \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome