From: Nikita Danilov <Nikita@Namesys.COM>
To: Christoph Hellwig <hch@infradead.org>
Cc: Nicholas Wourms <dragon@gentoo.org>,
Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remove kdevname() before someone starts using it again
Date: Mon, 7 Apr 2003 12:43:14 +0400 [thread overview]
Message-ID: <16017.14882.696046.660762@laputa.namesys.com> (raw)
In-Reply-To: <20030407091923.B28879@infradead.org>
Christoph Hellwig writes:
> On Mon, Apr 07, 2003 at 11:43:01AM +0400, Nikita Danilov wrote:
> > Nicholas Wourms writes:
> > >
> > > A quick grep shows that Intermezzo FS still uses kdevname if
> > > you've turned on debugging (fs/intermezzo/sysctl.c). As for
> > > pending stuff, both Reiser4 & pktcdvd also use it. So I
> >
> > reiser4 switched to bdevname().
>
> Although bdevname is the simplest replacement it's usually the wrong
> one. If you refer to a filesystem with it use sb->s_id, if you refer
> to a block device you normally want to use partition_name() - it gives
> much nicer output.
Thank you for the information.
We need something to name per super block directory under
/sys/fs/reiser4. It probably makes sense to have a convention for this
shared by all file systems living on top of block devices, like using
sb->s_id.
>
Nikita.
next prev parent reply other threads:[~2003-04-07 8:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 14:26 [PATCH] remove kdevname() before someone starts using it again Christoph Hellwig
2003-04-06 20:28 ` Nicholas Wourms
2003-04-06 20:35 ` Christoph Hellwig
2003-04-07 7:43 ` Nikita Danilov
2003-04-07 8:19 ` Christoph Hellwig
2003-04-07 8:39 ` Andrew Morton
2003-04-07 8:43 ` Nikita Danilov [this message]
2003-04-07 14:08 ` Nicholas Wourms
2003-04-07 14:25 ` Nikita Danilov
2003-04-07 14:35 ` Nicholas Wourms
2003-04-07 14:56 ` Oleg Drokin
2003-04-07 14:54 ` Oleg Drokin
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=16017.14882.696046.660762@laputa.namesys.com \
--to=nikita@namesys.com \
--cc=dragon@gentoo.org \
--cc=hch@infradead.org \
--cc=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