[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y4e90zFnhhq764lP@slm.duckdns.org>
Date: Wed, 30 Nov 2022 10:32:19 -1000
From: Tejun Heo <tj@...nel.org>
To: Li Nan <linan122@...wei.com>
Cc: josef@...icpanda.com, axboe@...nel.dk, cgroups@...r.kernel.org,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
yukuai3@...wei.com, yi.zhang@...wei.com
Subject: Re: [PATCH -next v2 2/9] blk-iocost: improve hanlder of match_u64()
On Wed, Nov 30, 2022 at 09:21:49PM +0800, Li Nan wrote:
> From: Yu Kuai <yukuai3@...wei.com>
>
> 1) There are one place that return value of match_u64() is not checked.
> 2) If match_u64() failed, return value is set to -EINVAL despite that
> there are other possible errnos.
Ditto. Does this matter?
--
tejun
Powered by blists - more mailing lists