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:05:38 +0000 (09:05 +0100)
commit92f337cd60b257dbab31382b420a2b3ccc02bb88
tree8fef95f19d31d7ca0ef2cfd17323bee1d4c004d2
parent1cd9b63ddda66a5ebdc2a7b98e07095a2d54080b
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