From: Nate Case <ncase@xes-inc.com>
To: Andy Fleming <afleming@freescale.com>
Cc: Olof Johansson <olof@lixom.net>,
netdev@vger.kernel.org, pasemi-linux@ozlabs.org
Subject: Re: [Pasemi-linux] I2C MDIO support for pasemi_mac driver
Date: Thu, 03 Apr 2008 08:45:27 -0500 [thread overview]
Message-ID: <1207230327.19618.62.camel@localhost.localdomain> (raw)
In-Reply-To: <C3F69A6B-85D0-4FB4-834E-958A21C7577A@freescale.com>
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@xes-inc.com>
prev parent reply other threads:[~2008-04-03 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1204911643.8864.15.camel@localhost.localdomain>
2008-03-07 18:37 ` I2C MDIO support for pasemi_mac driver Olof Johansson
2008-03-07 18:48 ` [Pasemi-linux] " Olof Johansson
2008-03-07 19:28 ` Nathaniel Case
2008-03-13 21:57 ` Nate Case
2008-04-02 22:45 ` Andy Fleming
2008-04-03 13:45 ` Nate Case [this message]
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=1207230327.19618.62.camel@localhost.localdomain \
--to=ncase@xes-inc.com \
--cc=afleming@freescale.com \
--cc=netdev@vger.kernel.org \
--cc=olof@lixom.net \
--cc=pasemi-linux@ozlabs.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.