mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>,
	Jonathan Corbet <corbet@lwn.net>, <linux-doc@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Documentation/, SPDX tags, and checkpatch.pl
Date: Mon, 14 Oct 2019 13:47:42 -0700	[thread overview]
Message-ID: <124ecffe-25a0-ace6-f106-d9d173c17035@nvidia.com> (raw)

Hi,

When adding a new Documentation/ file, checkpatch.pl is warning me
that the SPDX tag is missing. Should checkpatch.pl skip those kinds
of warnings, seeing as how we probably don't intend on putting the
SPDX tags at the top of the Documentation/*.rst files?

Or are we, after all? I'm just looking to get to a warnings-free situation 
here, one way or the other. :)

The exact warning I'm seeing is:

WARNING: Missing or malformed SPDX-License-Identifier tag in line 1
#25: FILE: Documentation/vm/get_user_pages.rst:1:
+.. _get_user_pages:


-- 
thanks,

John Hubbard
NVIDIA

             reply	other threads:[~2019-10-14 20:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14 20:47 John Hubbard [this message]
2019-10-14 20:55 ` Joe Perches
2019-10-14 21:02   ` John Hubbard

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=124ecffe-25a0-ace6-f106-d9d173c17035@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=apw@canonical.com \
    --cc=corbet@lwn.net \
    --cc=joe@perches.com \
    --cc=linux-doc@vger.kernel.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

all inboxes | Powered by JetHome®