On Wed, 29 May 2019, Hariprasad Kelam wrote: > dont acquire lock before calling wd719x_chip_init. > > Issue identified by coccicheck > > Signed-off-by: Hariprasad Kelam <hariprasad.ke...@gmail.com> > ----- > changes in v1: Replace GFP_KERNEL with GFP_ATOMIC. > changes in v2: Call wd719x_chip_init without lock as suggested > in review
Why was host_lock taken here initially? I assume it's to protect some race in init that leads to an undefined state.
