From: Andre Przywara <andre.przywara@arm.com>
To: Jagan Teki <jagan@amarulasolutions.com>
Cc: Samuel Holland <samuel@sholland.org>,
Tom Rini <trini@konsulko.com>,
u-boot@lists.denx.de, linux-sunxi@lists.linux.dev
Subject: [PATCH 2/4] sunxi: remove bogus mmc_pinmux_setup() prototype
Date: Wed, 14 Dec 2022 00:22:42 +0000 [thread overview]
Message-ID: <20221214002244.31479-3-andre.przywara@arm.com> (raw)
In-Reply-To: <20221214002244.31479-1-andre.przywara@arm.com>
Since all callers of mmc_pinmux_setup() are located after the definition
of that function, there is no need for a forward declaration (anymore?).
Remove the prototype along with its #ifdef guards.
Signed-off-by: Andre Przywara <andre.przywara@arm.com>
---
board/sunxi/board.c | 4 ----
1 file changed, 4 deletions(-)
diff --git a/board/sunxi/board.c b/board/sunxi/board.c
index 4d2491b5a86..4fe749feb39 100644
--- a/board/sunxi/board.c
+++ b/board/sunxi/board.c
@@ -184,10 +184,6 @@ enum env_location env_get_location(enum env_operation op, int prio)
return ENVL_UNKNOWN;
}
-#ifdef CONFIG_DM_MMC
-static void mmc_pinmux_setup(int sdc);
-#endif
-
/* add board specific code here */
int board_init(void)
{
--
2.35.5
next prev parent reply other threads:[~2022-12-14 0:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 0:22 [PATCH 0/4] sunxi: minor cleanups and refactoring Andre Przywara
2022-12-14 0:22 ` [PATCH 1/4] sunxi: remove unused CONFIG_MMC_SUNXI_SLOT Andre Przywara
2022-12-14 5:45 ` Samuel Holland
2022-12-14 0:22 ` Andre Przywara [this message]
2022-12-14 5:46 ` [PATCH 2/4] sunxi: remove bogus mmc_pinmux_setup() prototype Samuel Holland
2022-12-14 0:22 ` [PATCH 3/4] sunxi: board: annotate #endif lines Andre Przywara
2022-12-14 5:49 ` Samuel Holland
2022-12-14 0:22 ` [PATCH 4/4] sunxi: move arch timer setup out of board/ directory Andre Przywara
2022-12-14 6:14 ` Samuel Holland
2023-01-04 1:13 ` Andre Przywara
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=20221214002244.31479-3-andre.przywara@arm.com \
--to=andre.przywara@arm.com \
--cc=jagan@amarulasolutions.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=samuel@sholland.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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