Messages in this thread | | | Subject | Re: [PATCH][next] loop: Fix missing max_active argument in alloc_workqueue call | From | Jens Axboe <> | Date | Thu, 18 Mar 2021 14:12:10 -0600 |
| |
On 3/18/21 9:16 AM, Colin King wrote: > From: Colin Ian King <colin.king@canonical.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
| |