Amitkumar Karwar <akarwar@xxxxxxxxxxx> writes: > Hi Andreas, > > Thanks for the patch series. > >> >> Card reset is implemented by removing/re-adding the adapter instance. >> This is implemented by removing the mmc host, which will then trigger a >> cascade of removal callbacks including mwifiex_sdio_remove. >> The dead-lock results in the latter function, trying to cancel the work >> item executing the mmc host removal. This patch adds a driver level, not >> adapter level, work struct to break the dead-lock >> >> Signed-off-by: Andreas Fenkart <afenkart@xxxxxxxxx> >> --- >> drivers/net/wireless/mwifiex/main.h | 1 - >> drivers/net/wireless/mwifiex/sdio.c | 63 +++++++++++++++++++++++++++++-- >> ------ >> 2 files changed, 50 insertions(+), 14 deletions(-) >> > > We had recently submitted a patch to address this issue. So these two > patches won't be needed now. > http://www.spinics.net/lists/linux-wireless/msg135146.html > > Could you please check and let us know if you have any suggestions for > improvement? Ok, so we are talking about this commit which apparently fell through the cracks: https://git.kernel.org/cgit/linux/kernel/git/kvalo/wireless-drivers-next.git/commit/?id=2f5872b60146 Like I said as a reply to patch 1, using static variables for this is ugly. Isn't there really any better way to handle the problem? -- Kalle Valo -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
