From: Russell King <rmk@armlinux.org.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Nicolas Pitre <nico@linaro.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: linux-next: build warning after merge of the arm tree
Date: Tue, 28 Nov 2017 23:31:19 +0000 [thread overview]
Message-ID: <20171128233119.GA19925@flint.armlinux.org.uk> (raw)
In-Reply-To: <20171129101637.1e4c7af3@canb.auug.org.au>
On Wed, Nov 29, 2017 at 10:16:37AM +1100, Stephen Rothwell wrote:
> Hi Russell,
>
> After merging the arm tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> arch/arm/vfp/vfphw.S: Assembler messages:
> arch/arm/vfp/vfphw.S:158: Warning: conditional infixes are deprecated in unified syntax
> arch/arm/vfp/vfphw.S:233: Warning: conditional infixes are deprecated in unified syntax
> arch/arm/kernel/entry-common.S: Assembler messages:
> arch/arm/kernel/entry-common.S:285: Warning: conditional infixes are deprecated in unified syntax
> arch/arm/kernel/entry-common.S:286: Warning: conditional infixes are deprecated in unified syntax
> arch/arm/kernel/entry-common.S:365: Warning: conditional infixes are deprecated in unified syntax
>
> And many more similar.
>
> Presumably introduced by commit
>
> cabcafe5d1a5 ("ARM: 8723/1: always assume the "unified" syntax for assembly code")
Well, I seem to be missing all results from the various kernel build
systems, so I've no idea what's going on with those - although kernelci
has sent me boot results with no build results... our test systems
seem to be unreliable.
Dropping Nicolas' commit, there's obviously something wrong with it
somewhere. Nicolas, can you reproduce these problems?
--
Russell King
ARM architecture Linux Kernel maintainer
next prev parent reply other threads:[~2017-11-28 23:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 23:16 linux-next: build warning after merge of the arm tree Stephen Rothwell
2017-11-28 23:19 ` Russell King
2017-11-28 23:38 ` Stephen Rothwell
2017-11-28 23:41 ` Russell King
2017-11-29 6:58 ` Nicolas Pitre
2017-11-28 23:31 ` Russell King [this message]
2017-11-28 23:38 ` Nicolas Pitre
-- strict thread matches above, loose matches on Subject: below --
2014-11-18 8:25 Stephen Rothwell
2014-11-18 18:57 ` Stephen Boyd
2014-11-18 19:21 ` Russell King - ARM Linux
2014-11-18 19:43 ` Stephen Boyd
2014-04-22 0:32 Stephen Rothwell
2014-04-22 0:59 ` Sebastian Capella
2014-04-22 8:35 ` Russell King - ARM Linux
2014-04-23 16:43 ` Sebastian Capella
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=20171128233119.GA19925@flint.armlinux.org.uk \
--to=rmk@armlinux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nico@linaro.org \
--cc=robin.murphy@arm.com \
--cc=sfr@canb.auug.org.au \
/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).