From: w.sang@pengutronix.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 1/4] ARM: mxs: add GPMI-NAND support for imx23/imx28
Date: Fri, 8 Jul 2011 21:07:22 +0200 [thread overview]
Message-ID: <20110708190722.GA16490@pengutronix.de> (raw)
In-Reply-To: <1310102885-4102-2-git-send-email-b32955@freescale.com>
Hi Huang,
> diff --git a/arch/arm/mach-mxs/include/mach/gpmi-nand.h b/arch/arm/mach-mxs/include/mach/gpmi-nand.h
> new file mode 100644
> index 0000000..f1cf565
> --- /dev/null
> +++ b/arch/arm/mach-mxs/include/mach/gpmi-nand.h
I am also mostly happy with it now :)
Assuming the above file will be needed by mx50/mx6, too, would it make sense to
put it to include/linux/mtd/gpmi-nand.h right from the beginning?
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20110708/847a40ea/attachment-0001.sig>
next prev parent reply other threads:[~2011-07-08 19:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 5:28 [PATCH v6 0/4] add the GPMI-NAND support for imx23/imx28 Huang Shijie
2011-07-08 5:28 ` [PATCH v6 1/4] ARM: mxs: add " Huang Shijie
2011-07-08 6:53 ` Uwe Kleine-König
2011-07-08 7:01 ` Huang Shijie
2011-07-08 19:07 ` Wolfram Sang [this message]
2011-07-11 5:16 ` Huang Shijie
2011-07-08 5:28 ` [PATCH v6 2/4] ARM: mxs: add new a pad control Huang Shijie
2011-07-08 7:23 ` Uwe Kleine-König
2011-07-08 7:30 ` Huang Shijie
2011-07-08 5:28 ` [PATCH v6 3/4] ARM: mxs/mx23evk: add GPMI-NAND device Huang Shijie
2011-07-08 5:28 ` [PATCH v6 4/4] ARM: mxs/mx28evk: " Huang Shijie
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=20110708190722.GA16490@pengutronix.de \
--to=w.sang@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).