From: Arnd Bergmann <arnd@arndb.de>
To: linaro-dev@lists.linaro.org, ashish.jangam@kpitcummins.com
Cc: grant@secretlab.ca, Dajun <dajun.chen@diasemi.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
jic23@cam.ac.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 02/11] GPIO: DA9052 GPIO module v2
Date: Tue, 5 Jul 2011 16:43:44 +0200 [thread overview]
Message-ID: <201107051643.45158.arnd@arndb.de> (raw)
In-Reply-To: <1309872878.960.106.camel@L-0532.kpit.com>
On Tuesday 05 July 2011, ashishj3 wrote:
> DA9052 PMIC has 16 bit GPIO bus for peripheral control.
>
> This patch add support for the GPIO pins on the DA9052.
>
> Signed-off-by: David Dajun Chen <dchen@diasemi.com>
> Signed-off-by: Ashish Jangam <ashish.jangam@kpitcummins.com>
> CC: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> Changes since v2
> - change of file name
> - correct reference to irq_base in function to_irq()
> - remove pdata dependency
> ---
> drivers/gpio/Kconfig | 6 +
> drivers/gpio/Makefile | 1 +
> drivers/gpio/gpio-da9052.c | 259 +++++++++++++++++++++++++++++++++++++++
> include/linux/mfd/da9052/gpio.h | 47 +++++++
> 4 files changed, 313 insertions(+), 0 deletions(-)
I think I commented on this before, but please remove any header files
in include/linux that are not used as an interface between different
modules. If a header just describes properties of the hardware and is
used by a single source file, move the contents into that source file.
If a header is used by multiple files in one directory, make it a local
header in that directory.
Arnd
prev parent reply other threads:[~2011-07-05 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 13:34 [PATCH 02/11] GPIO: DA9052 GPIO module v2 ashishj3
2011-07-05 14:43 ` Arnd Bergmann [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=201107051643.45158.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=ashish.jangam@kpitcummins.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dajun.chen@diasemi.com \
--cc=grant@secretlab.ca \
--cc=jic23@cam.ac.uk \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.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