All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Altobelli, David" <david.altobelli@hp.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] HP iLO driver
Date: Thu, 12 Jun 2008 14:05:29 -0700	[thread overview]
Message-ID: <48518F99.7060003@zytor.com> (raw)
In-Reply-To: <CF70AA892F109448AEA269483B3A983903B6F79CCA@G1W1215.americas.hpqcorp.net>

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.

	-hpa

  reply	other threads:[~2008-06-12 21:06 UTC|newest]

Thread overview: 20+ 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-12 20:25     ` Jean Delvare
2008-06-13  2:51     ` John Stoffel
2008-06-13  2:51       ` John Stoffel
2008-06-13 19:39     ` 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 [this message]
2008-06-13  8:30       ` Michael Tokarev
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=48518F99.7060003@zytor.com \
    --to=hpa@zytor.com \
    --cc=david.altobelli@hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.