public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: linux-kernel@vger.kernel.org
Subject: [PATCH][RFC] remove devfs special casing from disk_name
Date: Sun, 4 May 2003 19:22:36 +0200	[thread overview]
Message-ID: <20030504192236.A10765@lst.de> (raw)

Currently disk_name() does some special casing to print the devfs
pathname for a gendisk instead of the disk_name as used all over the
kernel (which is the same/similar to the old-style device name but
not in any way connected to it).  There's two problems with this

 a) the devfs name is often too long for BDEVNAME_SIZE and thus
    gets truncated by snprintf
 b) having the kernel behave differently depending on whether devfs
    is compiled in or not is a bad thing.  One of my goals for 2.5
    is that devfs has no effect on the kernel except creating the
    devfs entries.

If there's some reason you can't live with the change below please
speak up (and no, "the devfs name looks prettier" or "it would confuse
Aunt Tillie" are not good enough arguments).


--- 1.108/fs/partitions/check.c	Tue Apr 29 17:42:50 2003
+++ edited/fs/partitions/check.c	Fri May  2 09:41:04 2003
@@ -96,19 +96,6 @@
 
 char *disk_name(struct gendisk *hd, int part, char *buf)
 {
-#ifdef CONFIG_DEVFS_FS
-	if (hd->devfs_name[0] != '\0') {
-		if (part)
-			snprintf(buf, BDEVNAME_SIZE, "%s/part%d",
-					hd->devfs_name, part);
-		else if (hd->minors != 1)
-			snprintf(buf, BDEVNAME_SIZE, "%s/disc", hd->devfs_name);
-		else
-			snprintf(buf, BDEVNAME_SIZE, "%s", hd->devfs_name);
-		return buf;
-	}
-#endif
-
 	if (!part)
 		snprintf(buf, BDEVNAME_SIZE, "%s", hd->disk_name);
 	else if (isdigit(hd->disk_name[strlen(hd->disk_name)-1]))

                 reply	other threads:[~2003-05-04 17:10 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=20030504192236.A10765@lst.de \
    --to=hch@lst.de \
    --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