From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] ARM i.MX: Move gpio initialization to SoC specific files
Date: Thu, 3 Mar 2011 11:34:34 +0100 [thread overview]
Message-ID: <20110303103434.GI29521@pengutronix.de> (raw)
In-Reply-To: <20110303102904.GC13179@n2100.arm.linux.org.uk>
On Thu, Mar 03, 2011 at 10:29:04AM +0000, Russell King - ARM Linux wrote:
> On Wed, Mar 02, 2011 at 12:01:20PM +0100, Sascha Hauer wrote:
> > diff --git a/arch/arm/mach-imx/mm-imx1.c b/arch/arm/mach-imx/mm-imx1.c
> > index 378c61b..8613e44 100644
> > --- a/arch/arm/mach-imx/mm-imx1.c
> > +++ b/arch/arm/mach-imx/mm-imx1.c
> > @@ -23,6 +23,8 @@
> >
> > #include <mach/common.h>
> > #include <mach/hardware.h>
> > +#include <mach/gpio.h>
>
> linux/gpio.h
I guessed that you would say that. I used mach/gpio.h intentionally
because I don't need the gpio functions but the
DEFINE_IMX_GPIO_PORT_IRQ_HIGH macro from this header. Should I use
linux/gpio.h anyway?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2011-03-03 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 11:01 [PATCH] i.MX some patches Sascha Hauer
2011-03-02 11:01 ` [PATCH 1/4] ARM i.MX: Move gpio initialization to SoC specific files Sascha Hauer
2011-03-03 10:29 ` Russell King - ARM Linux
2011-03-03 10:34 ` Sascha Hauer [this message]
2011-03-03 10:38 ` Russell King - ARM Linux
2011-03-02 11:01 ` [PATCH 2/4] ARM i.MX: iomux v1 initialization away from initcall Sascha Hauer
2011-03-02 11:01 ` [PATCH 3/4] ARM i.MX31 lilly: remove incomplete otg support Sascha Hauer
2011-03-02 11:01 ` [PATCH 4/4] ARM i.MX: introduce imx_otg_ulpi_create to create ULPI transceivers Sascha Hauer
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=20110303103434.GI29521@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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).