From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Rolf Eike Beer <eike-kernel@sf-tec.de>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] Use hex numbers in fs/block_dev.c
Date: Wed, 26 Feb 2003 17:37:38 +0100 [thread overview]
Message-ID: <20030226163738.GA15555@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <200302261719.15884@bilbo.math.uni-mannheim.de>
On Wed, 26 February 2003 17:19:15 +0100, Rolf Eike Beer wrote:
>
> We're using hex numbers to identify devices in most places. We should use
> them in filesystem messages, errors etc. too, this would be much more
> consistent and avoids things like this where two different naming styles
> for the same error are used:
>
> end_request: [...] dev 16:45 (hdd), sector 9175248
> EXT3-fs error (device ide1(22,69)): [...] inode=575269, block=1146906
>
> With this patch the second message would look like this:
>
> EXT3-fs error (device ide1(16:45)): [...] inode=575269, block=1146906
Whis is _horrible_. Am I supposed to guess that ide does not use major
16, so it will be 0x16 == 22 instead?
Better use the patch below, if at all.
--- linux-2.5.63-eike/fs/block_dev.c.orig Tue Feb 25 08:15:45 2003
+++ linux-2.5.63-eike/fs/block_dev.c Wed Feb 26 16:04:28 2003
@@ -794,7 +794,7 @@
if (!name)
name = "unknown-block";
- sprintf(buffer, "%s(%d,%d)", name, MAJOR(dev), MINOR(dev));
+ sprintf(buffer, "%s(0x%x:0x%x)", name, MAJOR(dev), MINOR(dev));
return buffer;
}
Jörn
--
Courage is not the absence of fear, but rather the judgement that
something else is more important than fear.
-- Ambrose Redmoon
next prev parent reply other threads:[~2003-02-26 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 16:19 Rolf Eike Beer
2003-02-26 16:37 ` Jörn Engel [this message]
2003-02-26 17:01 ` Rolf Eike Beer
2003-02-27 0:12 ` jw schultz
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=20030226163738.GA15555@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=eike-kernel@sf-tec.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®