From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Gregory CLEMENT <gregory.clement@bootlin.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: cm: Fix warning if MIPS_CM is disabled
Date: Wed, 19 Mar 2025 10:24:16 +0100 [thread overview]
Message-ID: <Z9qNQA_uyLG8bToX@alpha.franken.de> (raw)
In-Reply-To: <20250228143703.33381-1-tsbogend@alpha.franken.de>
On Fri, Feb 28, 2025 at 03:37:02PM +0100, Thomas Bogendoerfer wrote:
> Commit e27fbe16af5c ("MIPS: cm: Detect CM quirks from device tree")
> introduced
>
> arch/mips/include/asm/mips-cm.h:119:13: error: ‘mips_cm_update_property’
> defined but not used [-Werror=unused-function]
>
> Fix this by making empty function implementation inline
>
> Fixes: e27fbe16af5c ("MIPS: cm: Detect CM quirks from device tree")
> Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> ---
> arch/mips/include/asm/mips-cm.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/mips/include/asm/mips-cm.h b/arch/mips/include/asm/mips-cm.h
> index 3bfe0633b576..407f253bb4a1 100644
> --- a/arch/mips/include/asm/mips-cm.h
> +++ b/arch/mips/include/asm/mips-cm.h
> @@ -116,7 +116,7 @@ static inline bool mips_cm_present(void)
> #ifdef CONFIG_MIPS_CM
> extern void mips_cm_update_property(void);
> #else
> -static void mips_cm_update_property(void) {}
> +static inline void mips_cm_update_property(void) {}
> #endif
>
> /**
> --
> 2.35.3
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2025-03-19 10:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 14:37 [PATCH] MIPS: cm: Fix warning if MIPS_CM is disabled Thomas Bogendoerfer
2025-03-19 9:24 ` Thomas Bogendoerfer [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=Z9qNQA_uyLG8bToX@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=gregory.clement@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.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