[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <13a1d187-4d6d-9e06-b94a-553d872de756@kernel.dk>
Date: Thu, 18 Mar 2021 14:12:10 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Colin King <colin.king@...onical.com>,
Dan Schatzberg <schatzberg.dan@...il.com>,
linux-block@...r.kernel.org
Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH][next] loop: Fix missing max_active argument in
alloc_workqueue call
On 3/18/21 9:16 AM, Colin King wrote:
> From: Colin Ian King <colin.king@...onical.com>
>
> The 3rd argument to alloc_workqueue should be the max_active count,
> however currently it is the lo->lo_number that is intended for the
> loop%d number. Fix this by adding in the missing max_active count.
Dan, please fold this (or something similar) in when you're redoing the
series.
--
Jens Axboe
Powered by blists - more mailing lists