From: Guangshuo Li <lgs201920130244@gmail.com>
To: broonie@kernel.org, heiko@sntech.de, william.zhang@broadcom.com,
kursad.oney@broadcom.com, jonas.gorski@gmail.com
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
linusw@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, jon.lin@rock-chips.com,
bcm-kernel-feedback-list@broadcom.com, noltari@gmail.com,
lgs201920130244@gmail.com
Subject: [PATCH 0/3] spi: balance remove-path teardown in three drivers
Date: Thu, 24 Sep 2026 19:23:26 +0800 [thread overview]
Message-ID: <20260924112329.1566051-1-lgs201920130244@gmail.com> (raw)
Several SPI drivers establish resources or runtime-PM state during probe
but do not perform the matching teardown after successful removal.
Add the missing unmap or runtime-PM cleanup in each driver's remove path,
following the cleanup already used by its probe error paths.
Guangshuo Li (3):
spi: fsl: unmap immr_spi_cs on remove
spi: rockchip-sfc: Clean up runtime PM on remove
spi: bcm63xx-hsspi: Disable runtime PM on remove
drivers/spi/spi-bcm63xx-hsspi.c | 1 +
drivers/spi/spi-fsl-spi.c | 8 ++++++++
drivers/spi/spi-rockchip-sfc.c | 6 ++++++
3 files changed, 15 insertions(+)
base-commit: f03c39de3a1307371a4032757cd1732e91087c7d
--
2.43.0
next reply other threads:[~2026-09-24 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 11:23 Guangshuo Li [this message]
2026-09-24 11:23 ` [PATCH 1/3] spi: fsl: unmap immr_spi_cs on remove Guangshuo Li
2026-09-24 11:23 ` [PATCH 2/3] spi: rockchip-sfc: Clean up runtime PM " Guangshuo Li
2026-09-29 2:21 ` Shawn Lin
2026-09-24 11:23 ` [PATCH 3/3] spi: bcm63xx-hsspi: Disable " Guangshuo Li
2026-10-04 19:46 ` (subset) [PATCH 0/3] spi: balance remove-path teardown in three drivers Mark Brown
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=20260924112329.1566051-1-lgs201920130244@gmail.com \
--to=lgs201920130244@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=broonie@kernel.org \
--cc=heiko@sntech.de \
--cc=jon.lin@rock-chips.com \
--cc=jonas.gorski@gmail.com \
--cc=kursad.oney@broadcom.com \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=william.zhang@broadcom.com \
/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