netdev - Re: [Pasemi-linux] I2C MDIO support for pasemi

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <1207230327.19618.62.camel@localhost.localdomain>
Date:	Thu, 03 Apr 2008 08:45:27 -0500
From:	Nate Case <ncase@...-inc.com>
To:	Andy Fleming <afleming@...escale.com>
Cc:	Olof Johansson <olof@...om.net>, netdev@...r.kernel.org,
	pasemi-linux@...abs.org
Subject: Re: [Pasemi-linux] I2C MDIO support for pasemi_mac driver

On Wed, 2008-04-02 at 17:45 -0500, Andy Fleming wrote:
> My first instinct is that the current bus->id shouldn't be an int at  
> all (well, obviously not my *first* instinct, since that's what I did  
> the first time through).  So I like the idea of including a label in  
> the bus, but I'm not sure if it's necessary to add a new field.   
> Instead, I'd like to see bus->id converted to a char * or char [].  I  
> played around with this a bit today, and it requires a little more  
> work than it might at first seem, but is quite doable.
> 
> The question is whether that would solve your problem.  I think you  
> would then be able to register buses with the id "pas_gpio:xxx" or  
> "i2c:xxx", etc.

Thanks for the feedback.  Changing the bus ID to a string would solve my
problem, and I think this is a good way to do it.

- Nate Case <ncase@...-inc.com>

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html