mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kemeng Shi <shikemeng@huawei.com>
To: <tj@kernel.org>, <axboe@kernel.dk>
Cc: <cgroups@vger.kernel.org>, <linux-block@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] A few cleanup patches for blk-iolatency.c
Date: Mon, 17 Oct 2022 10:06:53 +0800	[thread overview]
Message-ID: <b25560e2-78ae-b501-ff2b-ad69fd5c0f49@huawei.com> (raw)
In-Reply-To: <20220929074055.30080-1-shikemeng@huawei.com>

Friendly ping ...

on 9/29/2022 3:40 PM, Kemeng Shi wrote:
> This series contains three cleanup patches to remove redundant check,
> correct comment and simplify struct iolatency_grp in blk-iolatency.c.
> 
> Kemeng Shi (3):
>   block: Remove redundant parent blkcg_gp check in check_scale_change
>   block: Correct comment for scale_cookie_change
>   block: Replace struct rq_depth with unsigned int in struct
>     iolatency_grp
> 
>  block/blk-iolatency.c | 33 ++++++++++++++-------------------
>  1 file changed, 14 insertions(+), 19 deletions(-)
> 

-- 
Best wishes
Kemeng Shi

      parent reply	other threads:[~2022-10-17  2:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29  7:40 Kemeng Shi
2022-09-29  7:40 ` [PATCH 1/3] block: Remove redundant parent blkcg_gp check in check_scale_change Kemeng Shi
2022-10-17 18:23   ` Josef Bacik
2022-09-29  7:40 ` [PATCH 2/3] block: Correct comment for scale_cookie_change Kemeng Shi
2022-10-17 18:20   ` Josef Bacik
2022-09-29  7:40 ` [PATCH 3/3] block: Replace struct rq_depth with unsigned int in struct iolatency_grp Kemeng Shi
2022-10-17 18:27   ` Josef Bacik
2022-10-17  2:06 ` Kemeng Shi [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=b25560e2-78ae-b501-ff2b-ad69fd5c0f49@huawei.com \
    --to=shikemeng@huawei.com \
    --cc=axboe@kernel.dk \
    --cc=cgroups@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@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

all inboxes | Powered by JetHome®