From: Matthew Wilcox <willy@debian.org>
To: Corey Minyard <minyard@acm.org>
Cc: Matthew Wilcox <willy@debian.org>, linux-kernel@vger.kernel.org
Subject: Re: [patch] Version 2 of the Linux IPMI driver
Date: Fri, 6 Sep 2002 21:36:52 +0100 [thread overview]
Message-ID: <20020906213652.G26580@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <3D790F2E.1050306@acm.org>; from minyard@acm.org on Fri, Sep 06, 2002 at 03:25:18PM -0500
On Fri, Sep 06, 2002 at 03:25:18PM -0500, Corey Minyard wrote:
> You access a device as a filesystem? That's bizarre. It's a device,
> and they call them "devices" in the kernel for a reason. Why would you
> want to do this? Especially with devfs, the whole device numbering
> problem goes away. You could easily make it a misc device.
The point is to get away from using character devices where we don't need
them (and we really don't need them in most places). Plus, there's no
dependency on devfs with this approach.
> Plus, your patch misses a lot of places where IPMI is going.
Oh, I'm quite aware of the limitations of my driver. I just don't
want to see yet another character device + ioctl interface going into
the kernel when it's really not necessary.
> And it wasn't stupid to call your "driver" BMC. That's exactly what it
> is. It's not IPMI, it's a KCS BMC interface (hooked in as a filesystem).
Right, but it should probably be addressed as /dev/ipmi since what we're
doing is sending IPMI messages.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2002-09-06 20:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-06 19:18 [patch] Version 2 of the Linux IPMI driver Matthew Wilcox
2002-09-06 20:25 ` Corey Minyard
2002-09-06 20:36 ` Matthew Wilcox [this message]
2002-09-09 17:07 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2002-09-06 18:35 Corey Minyard
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=20020906213652.G26580@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.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