linux-kernel - Re: [PATCH] HP iLO driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <48523012.1000007@msgid.tls.msk.ru>
Date:	Fri, 13 Jun 2008 12:30:10 +0400
From:	Michael Tokarev <mjt@....msk.ru>
To:	"H. Peter Anvin" <hpa@...or.com>
CC:	"Altobelli, David" <david.altobelli@...com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] HP iLO driver

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/