From: Jan Kara <jack@suse.cz>
To: "yukuai (C)" <yukuai3@huawei.com>
Cc: jack@suse.cz, tj@kernel.org, axboe@kernel.dk,
paolo.valente@linaro.org, cgroups@vger.kernel.org,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
yi.zhang@huawei.com
Subject: Re: [PATCH v2 0/3] block, bfq: minor cleanup and fix
Date: Fri, 14 Jan 2022 10:59:50 +0100 [thread overview]
Message-ID: <20220114095950.fa3gofecmryztivs@quack3.lan> (raw)
In-Reply-To: <1cdb99ba-ed52-c755-fec4-86ee5f9bc61d@huawei.com>
On Fri 14-01-22 16:23:36, yukuai (C) wrote:
> 在 2022/01/11 9:40, yukuai (C) 写道:
> > 在 2021/12/31 11:23, Yu Kuai 写道:
> > > Chagnes in v2:
> > > - add comment in patch 2
> > > - remove patch 4, since the problem do not exist.
> > >
> > friendly ping ...
>
> Hi, Jens
>
> Can this patchset be applied?
Maybe Jens is waiting for Paolo's ack as a BFQ maintainer. Paolo, what do
you think about the cleanups? They seem mostly obvious to me...
Honza
>
> Thanks
> > > Yu Kuai (3):
> > > block, bfq: cleanup bfq_bfqq_to_bfqg()
> > > block, bfq: avoid moving bfqq to it's parent bfqg
> > > block, bfq: don't move oom_bfqq
> > >
> > > block/bfq-cgroup.c | 16 +++++++++++++++-
> > > block/bfq-iosched.c | 4 ++--
> > > block/bfq-iosched.h | 1 -
> > > block/bfq-wf2q.c | 15 ---------------
> > > 4 files changed, 17 insertions(+), 19 deletions(-)
> > >
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2022-01-14 10:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 3:23 Yu Kuai
2021-12-31 3:23 ` [PATCH v2 1/3] block, bfq: cleanup bfq_bfqq_to_bfqg() Yu Kuai
2021-12-31 3:23 ` [PATCH v2 2/3] block, bfq: avoid moving bfqq to it's parent bfqg Yu Kuai
2021-12-31 3:23 ` [PATCH v2 3/3] block, bfq: don't move oom_bfqq Yu Kuai
2022-01-11 1:40 ` [PATCH v2 0/3] block, bfq: minor cleanup and fix yukuai (C)
2022-01-14 8:23 ` yukuai (C)
2022-01-14 9:59 ` Jan Kara [this message]
2022-01-18 17:53 ` Paolo Valente
2022-01-24 3:46 ` yukuai (C)
2022-01-28 9:35 ` yukuai (C)
2022-01-28 14:45 ` Jens Axboe
2022-01-28 19:27 ` Jens Axboe
2022-01-29 1:42 ` yukuai (C)
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=20220114095950.fa3gofecmryztivs@quack3.lan \
--to=jack@suse.cz \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.valente@linaro.org \
--cc=tj@kernel.org \
--cc=yi.zhang@huawei.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
all inboxes | Powered by JetHome®