From: Andrew Murray <andrew.murray@arm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Will Deacon <will.deacon@arm.com>,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: linux-next: build warnings after merge of the clockevents tree
Date: Mon, 17 Jun 2019 09:58:50 +0100 [thread overview]
Message-ID: <20190617085850.GH20984@e119886-lin.cambridge.arm.com> (raw)
In-Reply-To: <20190617145245.0e03163d@canb.auug.org.au>
On Mon, Jun 17, 2019 at 02:52:45PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the clockevents tree, today's linux-next build (arm
> multi_v7_defconfig) produced these warnings:
>
> In file included from arch/arm/kernel/vdso.c:30:
> arch/arm/include/asm/arch_timer.h: In function 'arch_timer_set_evtstrm_feature':
> arch/arm/include/asm/arch_timer.h:131:1: warning: no return statement in function returning non-void [-Wreturn-type]
> }
> ^
> In file included from drivers/clocksource/arm_arch_timer.c:31:
> arch/arm/include/asm/arch_timer.h: In function 'arch_timer_set_evtstrm_feature':
> arch/arm/include/asm/arch_timer.h:131:1: warning: no return statement in function returning non-void [-Wreturn-type]
> }
> ^
>
> Introduced by commit
>
> 11e34eca5d0a ("clocksource/arm_arch_timer: Extract elf_hwcap use to arch-helper")
This was also picked up by the kbuild robot, I'll sent a patch shortly - apologies.
Thanks,
Andrew Murray
>
> Look like a missed "return".
>
> --
> Cheers,
> Stephen Rothwell
prev parent reply other threads:[~2019-06-17 8:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 4:52 linux-next: build warnings after merge of the clockevents tree Stephen Rothwell
2019-06-17 8:58 ` Andrew Murray [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=20190617085850.GH20984@e119886-lin.cambridge.arm.com \
--to=andrew.murray@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=sfr@canb.auug.org.au \
--cc=will.deacon@arm.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