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 3/4] loop: remove most the top-of-file boilerplate comment
Date: Tue, 19 Apr 2022 08:33:02 +0200 [thread overview]
Message-ID: <20220419063303.583106-4-hch@lst.de> (raw)
In-Reply-To: <20220419063303.583106-1-hch@lst.de>
Remove the irrelevant changelogs and todo notes and just leave the SPDX
marker and the copyright notice.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
drivers/block/loop.c | 47 --------------------------------------------
1 file changed, 47 deletions(-)
diff --git a/drivers/block/loop.c b/drivers/block/loop.c
index b87151b60dc20..919c96c15be87 100644
--- a/drivers/block/loop.c
+++ b/drivers/block/loop.c
@@ -1,54 +1,7 @@
// SPDX-License-Identifier: GPL-2.0-only
/*
- * linux/drivers/block/loop.c
- *
- * Written by Theodore Ts'o, 3/29/93
- *
* Copyright 1993 by Theodore Ts'o.
- *
- * DES encryption plus some minor changes by Werner Almesberger, 30-MAY-1993
- * more DES encryption plus IDEA encryption by Nicholas J. Leon, June 20, 1996
- *
- * Modularized and updated for 1.1.16 kernel - Mitch Dsouza 28th May 1994
- * Adapted for 1.3.59 kernel - Andries Brouwer, 1 Feb 1996
- *
- * Fixed do_loop_request() re-entrancy - Vincent.Renardias@waw.com Mar 20, 1997
- *
- * Added devfs support - Richard Gooch <rgooch@atnf.csiro.au> 16-Jan-1998
- *
- * Handle sparse backing files correctly - Kenn Humborg, Jun 28, 1998
- *
- * Loadable modules and other fixes by AK, 1998
- *
- * Make real block number available to downstream transfer functions, enables
- * CBC (and relatives) mode encryption requiring unique IVs per data block.
- * Reed H. Petty, rhp@draper.net
- *
- * Maximum number of loop devices now dynamic via max_loop module parameter.
- * Russell Kroll <rkroll@exploits.org> 19990701
- *
- * Maximum number of loop devices when compiled-in now selectable by passing
- * max_loop=<1-255> to the kernel on boot.
- * Erik I. Bolsø, <eriki@himolde.no>, Oct 31, 1999
- *
- * Completely rewrite request handling to be make_request_fn style and
- * non blocking, pushing work to a helper thread. Lots of fixes from
- * Al Viro too.
- * Jens Axboe <axboe@suse.de>, Nov 2000
- *
- * Support up to 256 loop devices
- * Heinz Mauelshagen <mge@sistina.com>, Feb 2002
- *
- * Support for falling back on the write file operation when the address space
- * operations write_begin is not available on the backing filesystem.
- * Anton Altaparmakov, 16 Feb 2005
- *
- * Still To Fix:
- * - Advisory locking is ignored here.
- * - Should use an own CAP_* category instead of CAP_SYS_ADMIN
- *
*/
-
#include <linux/module.h>
#include <linux/moduleparam.h>
#include <linux/sched.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 ` Christoph Hellwig [this message]
2022-04-19 22:33 ` [PATCH 3/4] loop: remove most the top-of-file boilerplate comment Chaitanya Kulkarni
2022-04-19 6:33 ` [PATCH 4/4] loop: remove most the top-of-file boilerplate comment from the UAPI header Christoph Hellwig
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-4-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