From: Jiale Yao <yaojiale02@163.com>
To: Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Gatien Chevallier <gatien.chevallier@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Shawn Guo <shawnguo@kernel.org>,
Laurentiu Mihalcea <laurentiu.mihalcea@nxp.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
Huang Shijie <b32955@freescale.com>,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: [PATCH 0/3] bus: reject devices without platform match data
Date: Tue, 20 Oct 2026 17:36:32 +0800 [thread overview]
Message-ID: <20261020093637.1654161-1-yaojiale02@163.com> (raw)
Platform driver_override can bind a device to a platform driver without
matching its OF table. The match-data helpers then return NULL.
The i.MX AIPSTZ and WEIM drivers dereference the missing data during
probe. The STM32 RIFSC driver stores it for later dereference through
its debugfs configuration dump. Add checks before each first use so
these drivers reject unsupported devices instead of dereferencing NULL.
Each change is independent and can be applied separately.
Jiale Yao (3):
bus: imx-aipstz: reject devices without match data
bus: imx-weim: reject devices without match data
bus: stm32-rifsc: reject debugfs setup without match data
drivers/bus/imx-aipstz.c | 2 ++
drivers/bus/imx-weim.c | 6 +++++-
drivers/bus/stm32_rifsc.c | 2 ++
3 files changed, 9 insertions(+), 1 deletion(-)
--
2.34.1
next reply other threads:[~2026-10-20 9:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 9:36 Jiale Yao [this message]
2026-10-20 9:36 ` [PATCH 1/3] bus: imx-aipstz: reject devices without " Jiale Yao
2026-10-20 16:04 ` Frank Li
2026-10-20 9:36 ` [PATCH 2/3] bus: imx-weim: " Jiale Yao
2026-10-20 16:06 ` Frank Li
2026-10-20 9:36 ` [PATCH 3/3] bus: stm32-rifsc: reject debugfs setup " Jiale Yao
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=20261020093637.1654161-1-yaojiale02@163.com \
--to=yaojiale02@163.com \
--cc=Frank.Li@nxp.com \
--cc=alexandre.torgue@foss.st.com \
--cc=b32955@freescale.com \
--cc=daniel.baluta@nxp.com \
--cc=festevam@gmail.com \
--cc=gatien.chevallier@foss.st.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=laurentiu.mihalcea@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.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
all inboxes | Powered by JetHome®