From: Michael Tokarev <mjt@tls.msk.ru>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "Altobelli, David" <david.altobelli@hp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] HP iLO driver
Date: Fri, 13 Jun 2008 12:30:10 +0400 [thread overview]
Message-ID: <48523012.1000007@msgid.tls.msk.ru> (raw)
In-Reply-To: <48518F99.7060003@zytor.com>
H. Peter Anvin wrote:
> Altobelli, David wrote:
>>> Wouldn't /dev/hpilo/ccbN be a more appropriate namespace?
>>
>> Yes, that would be more clear. The code is currently defined to a
>> maximum of 1 hardware device, but this could change, and the dev path
>> should probably reflect that.
>>
>> How do you feel about /dev/hpiloX/ccbN, where X is 0, 1, ...
>> Num_Devices-1?
>
> I'd rather see /dev/hpilo/dXcY, the point being to try to declutter the
> /dev root.
For a case when there will be only one, or, in very rare theoretical
case, two devices, why bother in the first place? A subdirectory
containing only one node is more ugly.. ;)
/mjt
next prev parent reply other threads:[~2008-06-13 8:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 18:23 [PATCH] HP iLO driver David Altobelli
2008-06-12 18:34 ` 2.6.26-rc5: CFI: Found no ck804xrom @ffc00000 device at location zero John Stoffel
2008-06-12 20:25 ` Jean Delvare
2008-06-13 2:51 ` John Stoffel
2008-06-13 19:39 ` John Stoffel
2008-06-12 18:37 ` [PATCH] HP iLO driver H. Peter Anvin
2008-06-12 19:37 ` Altobelli, David
2008-06-12 21:05 ` H. Peter Anvin
2008-06-13 8:30 ` Michael Tokarev [this message]
2008-06-13 13:54 ` Altobelli, David
2008-06-12 20:13 ` Marcel Holtmann
2008-06-12 21:06 ` H. Peter Anvin
2008-06-12 19:04 ` Heikki Orsila
2008-06-12 20:16 ` Altobelli, David
-- strict thread matches above, loose matches on Subject: below --
2008-06-16 14:07 David Altobelli
2008-07-01 6:01 ` Andrew Morton
2008-07-01 21:01 ` Altobelli, David
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=48523012.1000007@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=david.altobelli@hp.com \
--cc=hpa@zytor.com \
--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