summaryrefslogtreecommitdiffstats
path: root/fs/f2fs
diff options
context:
space:
mode:
authorDouglas Anderson2019-04-04 06:01:06 +0200
committerKalle Valo2019-04-25 13:05:14 +0200
commitb82d6c1f8f8288f744a9dcc16cd3085d535decca (patch)
tree9920723ba38805e4099d4afd6a4bff3bbce2436d /fs/f2fs
parentMerge tag 'iwlwifi-for-kalle-2019-04-19' of git://git.kernel.org/pub/scm/linu... (diff)
downloadkernel-qcow2-linux-b82d6c1f8f8288f744a9dcc16cd3085d535decca.tar.gz
kernel-qcow2-linux-b82d6c1f8f8288f744a9dcc16cd3085d535decca.tar.xz
kernel-qcow2-linux-b82d6c1f8f8288f744a9dcc16cd3085d535decca.zip
mwifiex: Make resume actually do something useful again on SDIO cards
The commit fc3a2fcaa1ba ("mwifiex: use atomic bitops to represent adapter status variables") had a fairly straightforward bug in it. It contained this bit of diff: - if (!adapter->is_suspended) { + if (test_bit(MWIFIEX_IS_SUSPENDED, &adapter->work_flags)) { As you can see the patch missed the "!" when converting to the atomic bitops. This meant that the resume hasn't done anything at all since that commit landed and suspend/resume for mwifiex SDIO cards has been totally broken. After fixing this mwifiex suspend/resume appears to work again, at least with the simple testing I've done. Fixes: fc3a2fcaa1ba ("mwifiex: use atomic bitops to represent adapter status variables") Cc: <stable@vger.kernel.org> Signed-off-by: Douglas Anderson <dianders@chromium.org> Reviewed-by: Brian Norris <briannorris@chromium.org> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Diffstat (limited to 'fs/f2fs')
0 files changed, 0 insertions, 0 deletions