linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	Mark Salyzyn <salyzyn@android.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Shaokun Zhang <zhangshaokun@hisilicon.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: Tree for Oct 23
Date: Tue, 22 Oct 2019 23:56:02 -0700	[thread overview]
Message-ID: <46ae49f0-dbf0-0f11-3eba-e81197efbed0@infradead.org> (raw)
In-Reply-To: <CAMuHMdX1rhmvpWBHzvDYRNeYyotNp2ct1ysy4Jd0SjVUvGJd-Q@mail.gmail.com>

On 10/22/19 11:44 PM, Geert Uytterhoeven wrote:
> On Wed, Oct 23, 2019 at 8:17 AM Shaokun Zhang
> <zhangshaokun@hisilicon.com> wrote:
>> +Cc: Mark Salyzyn
>>
>> There is a compiler failure on arm64 platform, as follow:
>> zhangshaokun@ubuntu:~/linux-next$ make -j64
>>   CALL    scripts/atomic/check-atomics.sh
>>   CC      arch/arm64/kernel/asm-offsets.s
>> In file included from ./include/linux/sysctl.h:30:0,
>>                  from ./include/linux/umh.h:9,
>>                  from ./include/linux/kmod.h:9,
>>                  from ./include/linux/module.h:13,
>>                  from ./include/linux/acpi.h:29,
>>                  from ./include/acpi/apei.h:9,
>>                  from ./include/acpi/ghes.h:5,
>>                  from ./include/linux/arm_sdei.h:8,
>>                  from arch/arm64/kernel/asm-offsets.c:10:
>> ./include/uapi/linux/sysctl.h:561:29: error: expected ‘,’ or ‘}’ before ‘__attribute__’
>>   NET_IPV6_TEMP_PREFERED_LFT __attribute__((deprecated)) = /* NOTYPO */
>>                              ^
>> scripts/Makefile.build:99: recipe for target 'arch/arm64/kernel/asm-offsets.s' failed
>> make[1]: *** [arch/arm64/kernel/asm-offsets.s] Error 1
>> Makefile:1108: recipe for target 'prepare0' failed
>> make: *** [prepare0] Error 2
>>
>> It's the commit <79f0cf35dccb> ("treewide: cleanup: replace prefered with preferred").
> 
> After receiving a report from kisskb for failures for m68k, looking at
> http://kisskb.ellerman.id.au/kisskb/head/f3c452cfc59c817950b150b51ec2b33409d7640b/
> and doing some testing, it looks like this construct is supported by gcc-7
> and gcc-8, but not by gcc-4.6.3 and gcc-5. Don't know about gcc-6.

I guess that's a different problem than the misspelled PREFERED before the __attribute__.

-- 
~Randy

  reply	other threads:[~2019-10-23  6:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23  4:55 linux-next: Tree for Oct 23 Stephen Rothwell
2019-10-23  6:05 ` Shaokun Zhang
2019-10-23  6:44   ` Geert Uytterhoeven
2019-10-23  6:56     ` Randy Dunlap [this message]
2019-10-23  6:57     ` Shaokun Zhang
2019-10-23 15:46   ` Mark Salyzyn
2019-10-23 20:45     ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2023-10-23  5:58 Stephen Rothwell
2020-10-23  2:34 Stephen Rothwell
2014-10-23  4:21 Stephen Rothwell
2014-10-23 12:47 ` Stephen Rothwell
2013-10-23 15:13 Thierry Reding
2013-10-23 20:01 ` Guenter Roeck
2013-10-24  7:20 ` Sedat Dilek
2013-10-24  7:41   ` Thierry Reding
2012-10-23  4:19 Stephen Rothwell

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=46ae49f0-dbf0-0f11-3eba-e81197efbed0@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=salyzyn@android.com \
    --cc=sfr@canb.auug.org.au \
    --cc=zhangshaokun@hisilicon.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;
as well as URLs for NNTP newsgroup(s).