From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org,
Alexander Shiyan <eagle.alexander923@gmail.com>
Subject: Re: [PATCH] ARM: at91: remove unused soc type/subtype getter functions
Date: Fri, 20 Jun 2025 13:59:12 +0200 [thread overview]
Message-ID: <175042075298.3103799.100783308811640872.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250619103440.76796-1-eagle.alexander923@gmail.com>
On Thu, 19 Jun 2025 13:34:40 +0300, Alexander Shiyan wrote:
> The functions at91_get_soc_type() and at91_get_soc_subtype() were
> used only within the setup.c file. They provided simple access to
> string arrays but added an unnecessary layer of abstraction.
> Since they are not used elsewhere, we can safely remove them and
> access the string arrays directly.
>
>
> [...]
Applied, thanks!
[1/1] ARM: at91: remove unused soc type/subtype getter functions
https://git.pengutronix.de/cgit/barebox/commit/?id=a2a4de0237bc (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-06-20 12:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 10:34 Alexander Shiyan
2025-06-19 17:13 ` Sam Ravnborg
2025-06-20 5:48 ` Alexander Shiyan
2025-06-20 11:59 ` Sascha Hauer
2025-06-20 11:59 ` Sascha Hauer [this message]
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=175042075298.3103799.100783308811640872.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=eagle.alexander923@gmail.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