linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: X86 ML <x86@kernel.org>, open list <linux-kernel@vger.kernel.org>,
	lkft-triage@lists.linaro.org
Cc: Masahiro Yamada <masahiroy@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: x86: unistd_64.h: warning: missing whitespace after the macro name
Date: Mon, 24 May 2021 17:16:22 +0530	[thread overview]
Message-ID: <CA+G9fYvFXTHPKwasdVidF7qEHdqwRht8Xg6qm6CCLL0HGaU1ew@mail.gmail.com> (raw)

While building Linux next-20210524 tag with gcc 7.x the following warnings and
errors were noticed.

build log:
------------
  HOSTLD  scripts/mod/modpost
  CC      kernel/bounds.s
  CALL    /srv/oe/build/tmp-lkft-glibc/work-shared/intel-corei7-64/kernel-source/scripts/atomic/check-atomics.sh
  UPD     include/generated/bounds.h
  UPD     include/generated/timeconst.h
  CC      arch/x86/kernel/asm-offsets.s
In file included from
/srv/oe/build/tmp-lkft-glibc/work-shared/intel-corei7-64/kernel-source/arch/x86/include/asm/unistd.h:20:0,
                 from
/srv/oe/build/tmp-lkft-glibc/work-shared/intel-corei7-64/kernel-source/arch/x86/include/asm/seccomp.h:5,
                 from
/srv/oe/build/tmp-lkft-glibc/work-shared/intel-corei7-64/kernel-source/include/linux/seccomp.h:21,
                 from
/srv/oe/build/tmp-lkft-glibc/work-shared/intel-corei7-64/kernel-source/include/linux/sched.h:21,
                 from
/srv/oe/build/tmp-lkft-glibc/work-shared/intel-corei7-64/kernel-source/arch/x86/kernel/asm-offsets.c:10:
./arch/x86/include/generated/uapi/asm/unistd_64.h:4:14: warning:
missing whitespace after the macro name
 #define __NR_/usrread 0
              ^
./arch/x86/include/generated/uapi/asm/unistd_64.h:5:14: warning:
missing whitespace after the macro name
 #define __NR_/usrwrite 1
              ^
./arch/x86/include/generated/uapi/asm/unistd_64.h:5:0: warning:
"__NR_" redefined
 #define __NR_/usrwrite 1

./arch/x86/include/generated/uapi/asm/unistd_64.h:4:0: note: this is
the location of the previous definition
 #define __NR_/usrread 0

./arch/x86/include/generated/uapi/asm/unistd_64.h:6:14: warning:
missing whitespace after the macro name
 #define __NR_/usropen 2
              ^
./arch/x86/include/generated/uapi/asm/unistd_64.h:6:0: warning:
"__NR_" redefined
 #define __NR_/usropen 2

./arch/x86/include/generated/uapi/asm/unistd_64.h:5:0: note: this is
the location of the previous definition
 #define __NR_/usrwrite 1

./arch/x86/include/generated/uapi/asm/unistd_64.h:7:14: warning:
missing whitespace after the macro name
 #define __NR_/usrclose 3
              ^
./arch/x86/include/generated/uapi/asm/unistd_64.h:7:0: warning:
"__NR_" redefined
 #define __NR_/usrclose 3

./arch/x86/include/generated/uapi/asm/unistd_64.h:6:0: note: this is
the location of the previous definition
 #define __NR_/usropen 2

./arch/x86/include/generated/uapi/asm/unistd_64.h:8:14: warning:
missing whitespace after the macro name
 #define __NR_/usrstat 4
              ^
./arch/x86/include/generated/uapi/asm/unistd_64.h:8:0: warning:
"__NR_" redefined
 #define __NR_/usrstat 4

./arch/x86/include/generated/uapi/asm/unistd_64.h:7:0: note: this is
the location of the previous definition
 #define __NR_/usrclose 3

./arch/x86/include/generated/uapi/asm/unistd_64.h:9:14: warning:
missing whitespace after the macro name
 #define __NR_/usrfstat 5
              ^
./arch/x86/include/generated/uapi/asm/unistd_64.h:9:0: warning:
"__NR_" redefined
 #define __NR_/usrfstat 5

./arch/x86/include/generated/uapi/asm/unistd_64.h:8:0: note: this is
the location of the previous definition
 #define __NR_/usrstat 4

./arch/x86/include/generated/uapi/asm/unistd_64.h:10:14: warning:
missing whitespace after the macro name
 #define __NR_/usrlstat 6
              ^
./arch/x86/include/generated/uapi/asm/unistd_64.h:10:0: warning:
"__NR_" redefined
 #define __NR_/usrlstat 6

./arch/x86/include/generated/uapi/asm/unistd_64.h:9:0: note: this is
the location of the previous definition
 #define __NR_/usrfstat 5

<trim>

Reported-by: Naresh Kamboju <naresh.kamboju@linaro.org>

Detailed build link,
https://ci.linaro.org/view/lkft/job/openembedded-lkft-linux-next/DISTRO=lkft,MACHINE=intel-corei7-64,label=docker-buster-lkft/1032/console


--
Linaro LKFT
https://lkft.linaro.org

             reply	other threads:[~2021-05-24 11:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24 11:46 Naresh Kamboju [this message]
2021-05-25 10:54 ` x86: unistd_64.h: warning: missing whitespace after the macro name Thomas Gleixner
2021-05-25 11:56   ` Masahiro Yamada

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=CA+G9fYvFXTHPKwasdVidF7qEHdqwRht8Xg6qm6CCLL0HGaU1ew@mail.gmail.com \
    --to=naresh.kamboju@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=masahiroy@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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).