From: cengelma@gmx.at (Christian Engelmayer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: psci: fix warning on psci_init if ARM_PSCI is undefined
Date: Wed, 28 May 2014 23:46:06 +0200 [thread overview]
Message-ID: <20140528234606.47a9bdd2@spike> (raw)
In-Reply-To: <20140528075925.GF16428@lvm>
On Wed, 28 May 2014 09:59:25 +0200, Christoffer Dall <christoffer.dall@linaro.org> wrote:
> On Tue, May 27, 2014 at 11:20:47PM +0200, Christian Engelmayer wrote:
> > Commit e71246a (PSCI: Add initial support for PSCIv0.2 functions) changed the
> > return type of function psci_init() from void to int, but left the static
> > inline stub used if CONFIG_ARM_PSCI is not defined otherwise untouched. This
> > results in minor compile warning "warning: no return statement in function
> > returning non-void [-Wreturn-type]". The return value is currently not
> > evaluated by the only caller anyway.
> >
> > Signed-off-by: Christian Engelmayer <cengelma@gmx.at>
> > ---
> > Compile tested only. Applies against branch next in tree
> > git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git
>
> I sent out a fix for this yesterday as well, think Paolo was going to
> apply that one:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2014-May/260009.html
Thanks for letting me know Christoffer! I missed that when checking for already
submitted patches for this. Both patches only differ in the commit log message,
so it's fine either way.
Regards,
Christian
prev parent reply other threads:[~2014-05-28 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 21:20 [PATCH] ARM: psci: fix warning on psci_init if ARM_PSCI is undefined Christian Engelmayer
2014-05-28 7:59 ` Christoffer Dall
2014-05-28 21:46 ` Christian Engelmayer [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=20140528234606.47a9bdd2@spike \
--to=cengelma@gmx.at \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).