From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Joe Perches <joe@perches.com>
Cc: Nishad Kamdar <nishadkamdar@gmail.com>,
devel@driverdev.osuosl.org,
Forest Bond <forest@alittletooquiet.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: vt6656: Use the correct style for SPDX license Identifier
Date: Wed, 6 Feb 2019 17:25:24 +0100 [thread overview]
Message-ID: <20190206162524.GA22989@kroah.com> (raw)
In-Reply-To: <7771453cf380ce43d906f6648edecd8b58fec38a.camel@perches.com>
On Tue, Feb 05, 2019 at 10:59:40AM -0800, Joe Perches wrote:
> On Tue, 2019-02-05 at 19:44 +0100, Greg Kroah-Hartman wrote:
> > On Tue, Feb 05, 2019 at 08:36:24PM +0530, Nishad Kamdar wrote:
> > > This patch corrects the style for SPDX license Identifier in mac.h
> > > by using "/* */" in place of "//" as per Linux kernel licensing rules.
> > > Issue found by checkpatch.
> > >
> > > Signed-off-by: Nishad Kamdar <nishadkamdar@gmail.com>
> > > ---
> > > drivers/staging/vt6656/mac.h | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/staging/vt6656/mac.h b/drivers/staging/vt6656/mac.h
> > > index 94e700fcd0b6..75166020f7c6 100644
> > > --- a/drivers/staging/vt6656/mac.h
> > > +++ b/drivers/staging/vt6656/mac.h
> > > @@ -1,5 +1,5 @@
> > > -// SPDX-License-Identifier: GPL-2.0+
> > > -/*
> > > +/* SPDX-License-Identifier: GPL-2.0+
> >
> > Should really be:
> >
> > /* SPDX-License-Identifier: GPL-2.0+ */
>
> There's a fair number of style inconsistencies in the kernel
> sources for that already.
>
> ~8% of the .h files that have an 'SPDX-License-Identifier:'
> don't use the recommended style.
>
> $ git grep -h "SPDX-License" -- '*.h' | \
> perl -p -e 's@Identifier:.*\*/*@Identifier: ... */@; s@Identifier: [^\.].*@Identifier:@' | \
> sort | uniq -c | sort -rn
> 8506 /* SPDX-License-Identifier: ... */
> 593 // SPDX-License-Identifier:
> 154 /* SPDX-License-Identifier:
> 53 * SPDX-License-Identifier:
> 1 * SPDX-License-Identifier: GPL-2.0
> 1 //SPDX-License-Identifier:
> 1 /* SPDX-License-Identifier: ... */
Then let's fix them, the documentation says what the correct format is,
there's no reason we can't actually follow what is written...
next prev parent reply other threads:[~2019-02-06 16:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 15:06 [PATCH] staging: vt6656: Use the correct style for SPDX license Identifier Nishad Kamdar
2019-02-05 18:44 ` Greg Kroah-Hartman
2019-02-05 18:59 ` Joe Perches
2019-02-06 16:25 ` Greg Kroah-Hartman [this message]
2019-02-07 7:17 ` Joe Perches
2019-02-13 14:22 ` Nishad Kamdar
2019-02-12 15:09 ` Nishad Kamdar
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=20190206162524.GA22989@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=forest@alittletooquiet.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nishadkamdar@gmail.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