From: Miquel Raynal <miquel.raynal@bootlin.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH 00/14] mtd: Fix platform remove callbacks to always return 0
Date: Mon, 6 Jun 2022 15:18:41 +0200 [thread overview]
Message-ID: <20220606151841.682a5939@xps-13> (raw)
In-Reply-To: <20220603210758.148493-1-u.kleine-koenig@pengutronix.de>
Hi Folks,
u.kleine-koenig at pengutronix.de wrote on Fri, 3 Jun 2022 23:07:44 +0200:
> Hello,
>
> this series prepares to make platform remove callbacks return void.
> Therefor first update them to always return 0. The rationale is that the
> Linux device model doesn't handle failures on remove and if a remove
> callback returns an error, it just emits a quite generic error message
> and still removes the device.
Tudor, Pratyush, Richard, Vignesh,
The series looks good to me (besides the atmel patch), I think it's
best to take it directly through mtd/next instead of going through all
the different internal branches, please let me know if you disagree
with the idea.
Cheers,
Miqu?l
>
> Best regards
> Uwe
>
> Uwe Kleine-K?nig (14):
> mtd: hyperbus: Make hyperbus_unregister_device() return void
> mtd: spi-nor: aspeed-smc: Make aspeed_smc_unregister() return void
> mtd: powernv_flash: Warn about failure to unregister mtd device
> mtd: st-spi_fsm: Warn about failure to unregister mtd device
> mtd: lpddr2_nvm: Warn about failure to unregister mtd device
> mtd: spear_smi: Don't skip cleanup after mtd_device_unregister()
> failed
> mtd: spear_smi: Drop if with an always false condition
> mtd: rawnand: atmel: Warn about failure to unregister mtd device
> mtd: rawnand: omap2: Suppress error message after WARN in .remove()
> mtd: rawnand: tegra: Don't skip cleanup after mtd_device_unregister()
> failed
> mtd: rawnand: meson: Don't skip cleanup after mtd_device_unregister()
> failed
> mtd: rawnand: meson: Drop cleaning platform data in .remove()
> mtd: physmap: Don't skip cleanup after mtd_device_unregister() failed
> mtd: physmap: Drop if with an always false condition
>
> drivers/mtd/devices/powernv_flash.c | 4 +++-
> drivers/mtd/devices/spear_smi.c | 10 ++--------
> drivers/mtd/devices/st_spi_fsm.c | 4 +++-
> drivers/mtd/hyperbus/hbmc-am654.c | 6 +++---
> drivers/mtd/hyperbus/hyperbus-core.c | 8 ++------
> drivers/mtd/hyperbus/rpc-if.c | 5 +++--
> drivers/mtd/lpddr/lpddr2_nvm.c | 4 +++-
> drivers/mtd/maps/physmap-core.c | 13 +++----------
> drivers/mtd/nand/raw/atmel/nand-controller.c | 5 ++++-
> drivers/mtd/nand/raw/meson_nand.c | 16 +++-------------
> drivers/mtd/nand/raw/omap2.c | 6 ++----
> drivers/mtd/nand/raw/tegra_nand.c | 5 +----
> drivers/mtd/spi-nor/controllers/aspeed-smc.c | 8 ++++----
> include/linux/mtd/hyperbus.h | 4 +---
> 14 files changed, 37 insertions(+), 61 deletions(-)
>
> base-commit: 4b0986a3613c92f4ec1bdc7f60ec66fea135991f
next prev parent reply other threads:[~2022-06-06 13:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 21:07 [PATCH 00/14] mtd: Fix platform remove callbacks to always return 0 Uwe Kleine-König
2022-06-03 21:07 ` [PATCH 02/14] mtd: spi-nor: aspeed-smc: Make aspeed_smc_unregister() return void Uwe Kleine-König
2022-06-07 9:28 ` Pratyush Yadav
2022-06-07 9:54 ` Cédric Le Goater
2022-06-06 13:18 ` Miquel Raynal [this message]
2022-06-07 9:32 ` [PATCH 00/14] mtd: Fix platform remove callbacks to always return 0 Pratyush Yadav
2022-06-07 10:47 ` Miquel Raynal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220606151841.682a5939@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=linux-aspeed@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox