From: Jean Delvare <khali@linux-fr.org>
To: Bill Gatliff <bgat@billgatliff.com>
Cc: linuxppc-dev@ozlabs.org, lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] [RFC/PATCH 0/2] Updates to improve device tree support
Date: Thu, 7 Jan 2010 09:55:46 +0100 [thread overview]
Message-ID: <20100107095546.51d933af@hyperion.delvare> (raw)
In-Reply-To: <1262752236-1937-1-git-send-email-bgat@billgatliff.com>
Hi Bill,
On Tue, 5 Jan 2010 22:30:33 -0600, Bill Gatliff wrote:
> This patch series updates the pca953x GPIO driver to take advantage
> of the new of_i2c_gpiochip_add() function, which registers i2c GPIO
> devices with the device tree API. These changes allow i2c-based GPIO
> expanders to be properly referenced from the proper entries in a
> device tree.
>
> The of_i2c_gpiochip_add() function has been posted for review on the
> linuxppc-dev mailing list.
>
> Bill Gatliff (2):
> Use struct of_i2c_gpio_chip instead of raw struct gpio_chip
> Reorder initialization to better support device tree data
>
> drivers/gpio/pca953x.c | 168 +++++++++++++++++++++++++-----------------------
> 1 files changed, 88 insertions(+), 80 deletions(-)
This is totally off-topic for the lm-sensors mailing list, sorry.
--
Jean Delvare
prev parent reply other threads:[~2010-01-07 8:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 4:30 [RFC/PATCH 0/2] Updates to improve device tree support Bill Gatliff
2010-01-06 4:30 ` [PATCH 0/2] *** SUBJECT HERE *** Bill Gatliff
2010-01-06 4:30 ` [PATCH 1/2] Use struct of_i2c_gpio_chip instead of raw struct gpio_chip Bill Gatliff
2010-01-06 4:30 ` [PATCH 2/2] Reorder initialization to better support device tree data Bill Gatliff
2010-01-06 4:32 ` [PATCH 0/2] *** SUBJECT HERE *** Bill Gatliff
2010-01-07 8:55 ` Jean Delvare [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=20100107095546.51d933af@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=bgat@billgatliff.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=lm-sensors@lm-sensors.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 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).