From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>, "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-block@vger.kernel.org, linux-spdx@vger.kernel.org
Subject: [PATCH 4/4] loop: remove most the top-of-file boilerplate comment from the UAPI header
Date: Tue, 19 Apr 2022 08:33:03 +0200 [thread overview]
Message-ID: <20220419063303.583106-5-hch@lst.de> (raw)
In-Reply-To: <20220419063303.583106-1-hch@lst.de>
Just leave the SPDX marker and the copyright notice and remove the
irrelevant rest.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
include/uapi/linux/loop.h | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/include/uapi/linux/loop.h b/include/uapi/linux/loop.h
index 98e60801195e2..6f63527dd2ed6 100644
--- a/include/uapi/linux/loop.h
+++ b/include/uapi/linux/loop.h
@@ -1,11 +1,6 @@
/* SPDX-License-Identifier: GPL-1.0+ WITH Linux-syscall-note */
/*
- * include/linux/loop.h
- *
- * Written by Theodore Ts'o, 3/29/93.
- *
- * Copyright 1993 by Theodore Ts'o. Redistribution of this file is
- * permitted under the GNU General Public License.
+ * Copyright 1993 by Theodore Ts'o.
*/
#ifndef _UAPI_LINUX_LOOP_H
#define _UAPI_LINUX_LOOP_H
--
2.30.2
next prev parent reply other threads:[~2022-04-19 6:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 6:32 SPDX tag and top of file comment cleanups for the loop driver Christoph Hellwig
2022-04-19 6:33 ` [PATCH 1/4] loop: remove loop.h Christoph Hellwig
2022-04-19 22:32 ` Chaitanya Kulkarni
2022-05-10 12:30 ` Jens Axboe
2022-04-19 6:33 ` [PATCH 2/4] loop: add a SPDX header Christoph Hellwig
2022-04-19 6:33 ` [PATCH 3/4] loop: remove most the top-of-file boilerplate comment Christoph Hellwig
2022-04-19 22:33 ` Chaitanya Kulkarni
2022-04-19 6:33 ` Christoph Hellwig [this message]
2022-05-03 20:06 ` SPDX tag and top of file comment cleanups for the loop driver Theodore Ts'o
2022-05-03 20:13 ` Christoph Hellwig
2022-05-03 21:35 ` tytso
2022-05-10 7:22 ` Christoph Hellwig
2022-05-10 12:29 ` Jens Axboe
2022-05-10 13:58 ` Theodore Ts'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=20220419063303.583106-5-hch@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=tytso@mit.edu \
/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