public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Pool <mbp@sourcefrog.net>
To: linux-kernel@vger.kernel.org
Subject: [patch] trivial doc patch for partitions
Date: Tue, 27 Jul 2004 12:29:49 -0700	[thread overview]
Message-ID: <20040727192949.GC9564@happy.site> (raw)

It's slightly hard to see how these variables are used; this patch
adds a short description.

I am planning to change rescan_partitions so that it allows you to
change partitions on a disk that has active partitions, so long as the
active partitions themselves are not changed.  Would anyone object?


Index: linux-2.6/include/linux/fs.h
===================================================================
--- linux-2.6.orig/include/linux/fs.h	2004-06-18 15:16:35.000000000 -0700
+++ linux-2.6/include/linux/fs.h	2004-07-27 11:50:01.483618248 -0700
@@ -354,6 +354,7 @@
 	struct block_device *	bd_contains;
 	unsigned		bd_block_size;
 	struct hd_struct *	bd_part;
+	/* number of times partitions within this device have been opened. */
 	unsigned		bd_part_count;
 	int			bd_invalidated;
 	struct gendisk *	bd_disk;
Index: linux-2.6/include/linux/genhd.h
===================================================================
--- linux-2.6.orig/include/linux/genhd.h	2004-03-14 19:24:17.000000000 -0800
+++ linux-2.6/include/linux/genhd.h	2004-07-25 09:58:22.000000000 -0700
@@ -82,7 +82,8 @@
 struct gendisk {
 	int major;			/* major number of driver */
 	int first_minor;
-	int minors;
+	int minors;                     /* maximum number of minors, =1 for
+                                         * disks that can't be partitioned. */
 	char disk_name[32];		/* name of major driver */
 	struct hd_struct **part;	/* [indexed by minor] */
 	struct block_device_operations *fops;


-- 
Martin

                 reply	other threads:[~2004-07-27 19:30 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=20040727192949.GC9564@happy.site \
    --to=mbp@sourcefrog.net \
    --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