From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Carlos Henrique Lima Melara <charlesmelara@outlook.com>
Cc: "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"neil@brown.name" <neil@brown.name>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] staging: mt7621-eth/ethtool.c: Correction of SPDX license identifier
Date: Wed, 30 Jan 2019 22:12:31 +0100 [thread overview]
Message-ID: <20190130211231.GA25919@kroah.com> (raw)
In-Reply-To: <RO1P15201MB201234F951531D13328C4FF2A8900@RO1P15201MB2012.LAMP152.PROD.OUTLOOK.COM>
On Wed, Jan 30, 2019 at 08:01:13PM +0000, Carlos Henrique Lima Melara wrote:
> On 30/01/2019 13:29, gregkh@linuxfoundation.org wrote:
> > On Wed, Jan 30, 2019 at 02:48:27PM +0000, Carlos Henrique Lima Melara wrote:
> >> This patch fix the checkpatch.p1 warning:
> >>
> >> WARNING: Missing or malformed SPDX-License-Identifier tag in line 1
> >> +/*
> >
> > Why did you not fix up the indentation that was already mentioned?
>
> The Warning was about the missing SPDX License Identifier, so I added the
> identifier according to the "license-rules.rst" for C source that is:
I mean the indentation of the text in your changelog, nothing to do with
the actual change in your patch below, sorry for the confusion.
> > The SPDX license identifier is added in form of a comment. The comment
> > style depends on the file type::
> >
> > C source: // SPDX-License-Identifier: <SPDX License Expression>
> > C header: /* SPDX-License-Identifier: <SPDX License Expression> */
> > ASM: /* SPDX-License-Identifier: <SPDX License Expression> */
> > scripts: # SPDX-License-Identifier: <SPDX License Expression>
> > .rst: .. SPDX-License-Identifier: <SPDX License Expression>
> > .dts{i}: // SPDX-License-Identifier: <SPDX License Expression>
>
> I think that was the correction needed, right?
Yes.
> Still have a question about the license comment in the "ethtooll.c".
>
> > /* This program is free software; you can redistribute it and/or modify
> > * it under the terms of the GNU General Public License as published by
> > * the Free Software Foundation; version 2 of the License
> > *
> > * This program is distributed in the hope that it will be useful,
> > * but WITHOUT ANY WARRANTY; without even the implied warranty of
> > * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> > * GNU General Public License for more details.
> > *
> > * Copyright (C) 2009-2016 John Crispin <blogic@openwrt.org>
> > * Copyright (C) 2009-2016 Felix Fietkau <nbd@openwrt.org>
> > * Copyright (C) 2013-2016 Michael Lee <igvtee@gmail.com>
> > */
>
> It puts 3 spaces between the * and the text, should it be corrected to
> only one space?
If you really want to, but it's not needed.
All of the "boilerplate" license text can also be removed after the SPDX
line is added, if you want to do that. But leave the copyright lines,
that needs to stay.
thanks,
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-30 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 14:48 [PATCH v2] staging: mt7621-eth/ethtool.c: Correction of SPDX license identifier Carlos Henrique Lima Melara
2019-01-30 15:29 ` gregkh
2019-01-30 20:01 ` Carlos Henrique Lima Melara
2019-01-30 21:12 ` gregkh [this message]
2019-01-30 16:38 ` Andrew Lunn
2019-01-30 18:10 ` gregkh
2019-01-30 18:48 ` Andrew Lunn
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=20190130211231.GA25919@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=charlesmelara@outlook.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=neil@brown.name \
/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).