From: Oleksij Rempel <o.rempel@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Oleksij Rempel <o.rempel@pengutronix.de>
Subject: [PATCH v1 2/4] arm: boards: protonic-stm32mp13: Use unique board driver name
Date: Mon, 31 Mar 2025 14:30:30 +0200 [thread overview]
Message-ID: <20250331123032.626219-2-o.rempel@pengutronix.de> (raw)
In-Reply-To: <20250331123032.626219-1-o.rempel@pengutronix.de>
The driver was previously named "board-protonic-stm32", which is also
used by another board support file. This can lead to confusion when
both drivers are loaded, as it's hard to distinguish them in logs or
drvinfo output.
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
---
arch/arm/boards/protonic-stm32mp13/board.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boards/protonic-stm32mp13/board.c b/arch/arm/boards/protonic-stm32mp13/board.c
index 0173e3628dc3..d48a6dbf8e44 100644
--- a/arch/arm/boards/protonic-stm32mp13/board.c
+++ b/arch/arm/boards/protonic-stm32mp13/board.c
@@ -285,7 +285,7 @@ static const struct of_device_id prt_stm32_of_match[] = {
BAREBOX_DEEP_PROBE_ENABLE(prt_stm32_of_match);
static struct driver prt_stm32_board_driver = {
- .name = "board-protonic-stm32",
+ .name = "board-protonic-stm32mp13",
.probe = prt_stm32_probe,
.of_compatible = prt_stm32_of_match,
};
--
2.39.5
next prev parent reply other threads:[~2025-03-31 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 12:30 [PATCH v1 1/4] arm: boards: protonic-stm32mp13: Add support for MECT1S board Oleksij Rempel
2025-03-31 12:30 ` Oleksij Rempel [this message]
2025-03-31 12:30 ` [PATCH v1 3/4] arm: boards: protonic-stm32mp: fix stack corruption by passing correct ctx to stm32_bsec_optee_ta_close() Oleksij Rempel
2025-03-31 12:30 ` [PATCH v1 4/4] arm: boards: protonic-stm32mp: free shift register GPIOs after use Oleksij Rempel
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=20250331123032.626219-2-o.rempel@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=barebox@lists.infradead.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