mtd: mtdoops: Don't write panic data twice
authorMark Tomlinson <mark.tomlinson@alliedtelesis.co.nz>
Thu, 3 Sep 2020 03:42:17 +0000 (15:42 +1200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 29 Oct 2020 08:07:08 +0000 (09:07 +0100)
commitb26380cfbf0489ee9f88e68f466cf4cc00520ac3
treebae37261521da273e212ab232178c906b754365e
parent8f781b33b319798a5ffadc35101a01bb4f75d750
mtd: mtdoops: Don't write panic data twice

[ Upstream commit c1cf1d57d1492235309111ea6a900940213a9166 ]

If calling mtdoops_write, don't also schedule work to be done later.

Although this appears to not be causing an issue, possibly because the
scheduled work will never get done, it is confusing.

Fixes: 016c1291ce70 ("mtd: mtdoops: do not use mtd->panic_write directly")
Signed-off-by: Mark Tomlinson <mark.tomlinson@alliedtelesis.co.nz>
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Link: https://lore.kernel.org/linux-mtd/20200903034217.23079-1-mark.tomlinson@alliedtelesis.co.nz
Signed-off-by: Sasha Levin <sashal@kernel.org>
drivers/mtd/mtdoops.c