On Thu, Mar 18, 2021 at 03:16:26PM +0000, Colin King wrote: > From: Colin Ian King <colin.k...@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. >
Thanks for catching this Colin. I'm fairly new to kernel development. Is there some tool I could have run locally to catch this?
