From: Joe Perches <joe@perches.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-spdx@vger.kernel.org
Subject: Re: [GIT PULL] SPDX update for 5.2-rc1 - round 1
Date: Wed, 22 May 2019 19:57:41 -0700 [thread overview]
Message-ID: <4857dce766f161a643eb3340dfee6a2dec7eb2e5.camel@perches.com> (raw)
In-Reply-To: <CAK7LNAQ=M0ejV3C8bgjuMxdRR9v=2-GRdXeUjFR6URrrtYPCnA@mail.gmail.com>
On Thu, 2019-05-23 at 11:49 +0900, Masahiro Yamada wrote:
> On Wed, May 22, 2019 at 3:37 PM Joe Perches <joe@perches.com> wrote:
[]
> > I could also wire up a patch to checkpatch and docs to
> > remove the /* */ requirement for .h files and prefer
> > the generic // form for both .c and .h files as the
> > current minimum tooling versions now all allow //
> > comments
> > .
>
> We have control for minimal tool versions for building the kernel,
> so I think // will be OK for in-kernel headers.
>
>
> On the other hand, I am not quite sure about UAPI headers.
> We cannot define minimum tool versions
> for building user-space.
> Perhaps, using // in UAPI headers causes a problem
> if an ancient compiler is used?
Good point. Thanks.
next prev parent reply other threads:[~2019-05-23 2:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190521133257.GA21471@kroah.com>
2019-05-21 19:55 ` [GIT PULL] SPDX update for 5.2-rc1 - round 1 pr-tracker-bot
2019-05-21 19:56 ` Linus Torvalds
2019-05-22 16:34 ` Greg KH
2019-05-22 4:32 ` Masahiro Yamada
2019-05-22 6:34 ` Joe Perches
2019-05-22 10:14 ` Thomas Gleixner
2019-05-23 2:49 ` Masahiro Yamada
2019-05-23 2:57 ` Joe Perches [this message]
2019-05-23 5:33 ` Thomas Gleixner
2019-06-25 11:19 ` Masahiro Yamada
2019-05-29 13:13 ` Alexandre Belloni
2019-05-29 13:51 ` Thomas Gleixner
2019-05-29 14:16 ` Zavras, Alexios
[not found] ` <B03F305C-F579-43E1-BEE7-D628BD44FF48@jilayne.com>
2019-05-31 0:25 ` J Lovejoy
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=4857dce766f161a643eb3340dfee6a2dec7eb2e5.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=yamada.masahiro@socionext.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).