From: Chen Gang <gang.chen@asianux.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: [Consult] Do we need related web site link in "./COPYING" file?
Date: Fri, 08 Nov 2013 12:34:36 +0800 [thread overview]
Message-ID: <527C69DC.80901@asianux.com> (raw)
Hello All:
I guess COPYING is our GPL License file, it already contents related
Free Software Foundation address. Do we also need content related web
site link?
When make patch for "arch/arm64/include/uapi/", "scripts/checkpatch.pl"
will report the issue below:
ERROR: Do not include the paragraph about writing to the Free Software Foundation's mailing address from the sample GPL notice. The FSF has changed addresses in the past, and may do so again. Linux already includes a copy of the GPL.
#209: FILE: arch/arm64/include/uapi/asm/signal.h:13:
* You should have received a copy of the GNU General Public License$
I guess, "scrpits/checkpatch.pl" wants to say: "the Linux GPL copy
already contents related web site, so need not 'hard code' them in
another place".
BTW: I find some "^L" in COPYING file, are they for page separation?
Welcome any suggestions or completions.
Thanks.
--
Chen Gang
reply other threads:[~2013-11-08 4:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=527C69DC.80901@asianux.com \
--to=gang.chen@asianux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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