From: Nate Case <ncase@xes-inc.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: devicetree-discuss@ozlabs.org, linux-embedded@vger.kernel.org,
linuxppc-dev@ozlabs.org, linux-i2c@vger.kernel.org
Subject: Re: [RFC] misc/at24: add experimental OF support for the generic eeprom driver
Date: Fri, 09 Oct 2009 08:43:13 -0500 [thread overview]
Message-ID: <1255095793.16018.32.camel@localhost.localdomain> (raw)
In-Reply-To: <20091009051409.GA2361@pengutronix.de>
On Fri, 2009-10-09 at 07:14 +0200, Wolfram Sang wrote:
> And while doing this and figuring the pro/cons of those methods, I
> stumbled over this commit:
>
> gpio: pca953x: Get platform_data from OpenFirmware
> (1965d30356c1c65660ba3330927671cfe81acdd5)
Aside from any issues you have with the properties themselves, what's
your take on this approach?
Personally, I just got tired of waiting for someone else to solve the
pdata/OF problem. So I submitted that commit as an attempt at something
very simple and unobtrusive to the device driver itself. It seems
pretty clean to me, but I'm curious to see if others have any better
ideas.
- Nate
next prev parent reply other threads:[~2009-10-09 13:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1255010672-21656-1-git-send-email-w.sang@pengutronix.de>
[not found] ` <20091008143301.GA6084@oksana.dev.rtsoft.ru>
[not found] ` <fa686aa40910080753v6f597b0h4ce835db9f7a653@mail.gmail.com>
[not found] ` <20091008151007.GA21328@oksana.dev.rtsoft.ru>
2009-10-08 15:48 ` [RFC] misc/at24: add experimental OF support for the generic eeprom driver Grant Likely
2009-10-08 20:27 ` Wolfram Sang
2009-10-09 5:14 ` Wolfram Sang
[not found] ` <20091009051409.GA2361-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-10-09 5:40 ` Grant Likely
2009-10-09 14:01 ` Nate Case
2009-10-09 16:09 ` Grant Likely
2009-10-09 16:20 ` Wolfram Sang
2009-10-09 13:43 ` Nate Case [this message]
2009-10-09 16:12 ` Wolfram Sang
2009-10-09 16:13 ` Grant Likely
[not found] ` <fa686aa40910080848r459c47baob73fc70a95a08604-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-08 22:20 ` Anton Vorontsov
2009-10-09 6:37 ` Grant Likely
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=1255095793.16018.32.camel@localhost.localdomain \
--to=ncase@xes-inc.com \
--cc=devicetree-discuss@ozlabs.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=w.sang@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).