From: Masahiro Yamada <masahiroy@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
X86 ML <x86@kernel.org>, open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org
Subject: Re: x86: unistd_64.h: warning: missing whitespace after the macro name
Date: Tue, 25 May 2021 20:56:55 +0900 [thread overview]
Message-ID: <CAK7LNAR2iVHa6RvQMxpPJco0ruqWDHMyN3-qBM+wb+RfzTdzSA@mail.gmail.com> (raw)
In-Reply-To: <874ker9j8y.ffs@nanos.tec.linutronix.de>
On Tue, May 25, 2021 at 7:54 PM Thomas Gleixner <tglx@linutronix.de> wrote:
>
> On Mon, May 24 2021 at 17:16, Naresh Kamboju wrote:
>
> > 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
> > ^
>
> Where is that "/usr" coming from?
>
> Looking at the generator script this looks like a stale $prefix
> parameter...
Sorry, it is my mistake.
I submitted a fix.
https://lore.kernel.org/patchwork/patch/1435988/
--
Best Regards
Masahiro Yamada
prev parent reply other threads:[~2021-05-25 11:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 11:46 x86: unistd_64.h: warning: missing whitespace after the macro name Naresh Kamboju
2021-05-25 10:54 ` Thomas Gleixner
2021-05-25 11:56 ` Masahiro Yamada [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=CAK7LNAR2iVHa6RvQMxpPJco0ruqWDHMyN3-qBM+wb+RfzTdzSA@mail.gmail.com \
--to=masahiroy@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.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).