[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7cb40388-02e9-712a-6a40-ccabd5605880@kernel.dk>
Date: Fri, 28 Jan 2022 18:51:42 -0700
From: Jens Axboe <axboe@...nel.dk>
To: Yu Kuai <yukuai3@...wei.com>, paolo.valente@...aro.org,
jack@...e.cz
Cc: linux-block@...r.kernel.org, cgroups@...r.kernel.org,
linux-kernel@...r.kernel.org, yi.zhang@...wei.com
Subject: Re: [PATCH v3 0/3] block, bfq: minor cleanup and fix
On 1/28/22 6:59 PM, Yu Kuai wrote:
> Changes in v3:
> - fix a clerical error in patch 2
>
> Chagnes in v2:
> - add comment in patch 2
> - remove patch 4, since the problem do not exist.
>
> 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(-)
I'm not even looking at this until you tell me that:
a) you've actually compiled this one. which, btw, I can't believe
needs mentioning, particularly when you had enough time to keep
pinging about this patchset.
b) it's actually be run. last one was clearly not.
--
Jens Axboe
Powered by blists - more mailing lists