From: Dave Jones <davej@codemonkey.org.uk>
To: Christoph Hellwig <hch@infradead.org>,
David Ford <david+cert@blue-labs.org>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.66 buglet
Date: Fri, 28 Mar 2003 11:11:17 +0000 [thread overview]
Message-ID: <20030328111117.GB32101@suse.de> (raw)
In-Reply-To: <20030328082607.A13326@infradead.org>
On Fri, Mar 28, 2003 at 08:26:07AM +0000, Christoph Hellwig wrote:
> > > + error = devfs_mk_symlink("cpu/microcode", "../misc/microcode");
> > Where did ../misc/microcode come from? That sounds horribly
> > generic compared to /dev/cpu/microcode
>
> devfs automatically registers /dev/misc/<name> entries for any minor
> registered by misc_register.
That's pretty fucked up IMO. Is it feasable that we could one day
have /dev/$otherhardware/microcode, and that would completely
screw up this devfs 'feature' ?
Dave
prev parent reply other threads:[~2003-03-28 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 4:23 2.5.66 buglet David Ford
2003-03-27 14:54 ` Christoph Hellwig
2003-03-27 23:30 ` Dave Jones
2003-03-28 8:26 ` Christoph Hellwig
2003-03-28 11:11 ` Dave Jones [this message]
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=20030328111117.GB32101@suse.de \
--to=davej@codemonkey.org.uk \
--cc=david+cert@blue-labs.org \
--cc=hch@infradead.org \
--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