From: Suzuki K Poulose <Suzuki.Poulose@arm.com>
To: Baoyou Xie <baoyou.xie@linaro.org>,
will.deacon@arm.com, olof@lixom.net, mark.rutland@arm.com,
bigeasy@linutronix.de, a.hajda@samsung.com
Cc: linux-kernel@vger.kernel.org, arnd@arndb.de, xie.baoyou@zte.com.cn
Subject: Re: [PATCH] arm-cci: add cci_enable_port_for_self() declaration in arm-cci.h
Date: Mon, 12 Sep 2016 11:35:38 +0100 [thread overview]
Message-ID: <641df89f-541e-dea1-4144-2c6d43fac7b2@arm.com> (raw)
In-Reply-To: <1473676381-11049-1-git-send-email-baoyou.xie@linaro.org>
On 12/09/16 11:33, Baoyou Xie wrote:
> We get 1 warning when building kernel with W=1:
> drivers/bus/arm-cci.c:2027:25: warning: no previous prototype for 'cci_enable_port_for_self' [-Wmissing-prototypes]
>
> In fact, this function is used in a few files,
> but should be declared in a header file.
>
> So this patch adds the declaration in arm-cci.h.
>
> Signed-off-by: Baoyou Xie <baoyou.xie@linaro.org>
> ---
> include/linux/arm-cci.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/linux/arm-cci.h b/include/linux/arm-cci.h
> index 521ec1f..b88f6fb 100644
> --- a/include/linux/arm-cci.h
> +++ b/include/linux/arm-cci.h
> @@ -30,8 +30,10 @@ struct device_node;
>
> #ifdef CONFIG_ARM_CCI
> extern bool cci_probed(void);
> +extern asmlinkage void __naked cci_enable_port_for_self(void);
> #else
> static inline bool cci_probed(void) { return false; }
> +static inline void ci_enable_port_for_self(void) { return; }
> #endif
>
Don't you think the above definitions should depend on
ARM_CCI400_PORT_CTRL than ARM_CCI ?
Suzuki
next prev parent reply other threads:[~2016-09-12 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 10:33 Baoyou Xie
2016-09-12 10:35 ` Suzuki K Poulose [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-12 10:30 Baoyou Xie
2016-09-12 18:44 ` kbuild test robot
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=641df89f-541e-dea1-4144-2c6d43fac7b2@arm.com \
--to=suzuki.poulose@arm.com \
--cc=a.hajda@samsung.com \
--cc=arnd@arndb.de \
--cc=baoyou.xie@linaro.org \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=will.deacon@arm.com \
--cc=xie.baoyou@zte.com.cn \
/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®