From: "Tomasz Warniełło" <tomasz.warniello@gmail.com>
To: corbet@lwn.net
Cc: "Tomasz Warniełło" <tomasz.warniello@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 13/15] scripts: kernel-doc: Transform documentation into POD (13/15)
Date: Mon, 3 Jan 2022 05:55:45 +0100 [thread overview]
Message-ID: <20220103045547.506783-3-tomasz.warniello@gmail.com> (raw)
In-Reply-To: <20220103045547.506783-1-tomasz.warniello@gmail.com>
Step 13) License cleanup
As stated by Jonathan Corbet in the reply to my version 1, the SPDX line is
enough.
See step 1 for the series details.
(Still not sure about this tag line, so please correct if needed.)
Suggested-by: Jonathan Corbet <corbet@lwn.net>
Signed-off-by: Tomasz Warniełło <tomasz.warniello@gmail.com>
---
scripts/kernel-doc | 3 ---
1 file changed, 3 deletions(-)
diff --git a/scripts/kernel-doc b/scripts/kernel-doc
index 51e813a84d8b..eb56770b96c5 100755
--- a/scripts/kernel-doc
+++ b/scripts/kernel-doc
@@ -12,9 +12,6 @@ use strict;
## ##
## #define enhancements by Armin Kuster <akuster@mvista.com> ##
## Copyright (c) 2000 MontaVista Software, Inc. ##
-## ##
-## This software falls under the GNU General Public License. ##
-## Please read the COPYING file for more information ##
use Pod::Usage qw/pod2usage/;
--
2.30.2
next prev parent reply other threads:[~2022-01-03 4:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 4:55 [PATCH v2 11/15] scripts: kernel-doc: Transform documentation into POD (11/15) Tomasz Warniełło
2022-01-03 4:55 ` [PATCH v2 12/15] scripts: kernel-doc: Transform documentation into POD (12/15) Tomasz Warniełło
2022-01-03 4:55 ` Tomasz Warniełło [this message]
2022-01-03 4:55 ` [PATCH v2 14/15] scripts: kernel-doc: Transform documentation into POD (14/15) Tomasz Warniełło
2022-01-03 4:55 ` [PATCH v2 15/15] scripts: kernel-doc: Transform documentation into POD (15/15) Tomasz Warniełło
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=20220103045547.506783-3-tomasz.warniello@gmail.com \
--to=tomasz.warniello@gmail.com \
--cc=corbet@lwn.net \
--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
Powered by JetHome