From: Tony Lindgren <tony@atomide.com>
To: dedekind@infradead.org, juha.yrjola@solidboot.com,
linux-omap@vger.kernel.org, adrian.hunter@nokia.com
Subject: Re: [PATCH 0/7] Generic gpmc-onenand initialization, v3
Date: Wed, 6 May 2009 11:07:24 -0700 [thread overview]
Message-ID: <20090506180722.GN5593@atomide.com> (raw)
In-Reply-To: <20090505002144.2894.25201.stgit@localhost>
* Tony Lindgren <tony@atomide.com> [090504 17:25]:
> Hi all,
>
> Here's the whole series one more time, looks like I missed Juha
> from the recipients originally. After all it's mostly Juha's
> code! :)
>
> To recap, this series creates a generic gpmc-onenand.c out of the
> board-n800-flash.c so we can get this init code to the mainline
> kernel. This series is against the linux-omap tree, the patch
> against the mainline tree will be posted later.
Pushing this series to linux-omap tree today.
> Regards,
>
> Tony
>
> ---
>
> Tony Lindgren (7):
> onenand_init: Clean-up for checkpatch.pl
> onenand init: Convert omap3430sdp to use gpmc-onenand
> onenand_init: Allow disabling sync read and write based on flags, v3
> onenand init: Pass configuration data from board-*.c files
> onenand init: Rename n800_* functions to gpmc_onenand_* functions
> onenand init: Build gpmc-onenand.o based on CONFIG_MTD_ONENAND_OMAP2
> onenand init: Rename board-n800-flash.c to gpmc-onenand.c
>
>
> arch/arm/mach-omap2/Makefile | 7 +-
> arch/arm/mach-omap2/board-3430sdp-flash.c | 28 -------
> arch/arm/mach-omap2/board-n800.c | 50 ++++++++++++
> arch/arm/mach-omap2/board-rx51-flash.c | 21 -----
> arch/arm/mach-omap2/board-rx51-peripherals.c | 47 ++++++++++++
> arch/arm/mach-omap2/board-rx51.c | 2
> arch/arm/mach-omap2/gpmc-onenand.c | 105 ++++++++++++--------------
> arch/arm/plat-omap/include/mach/board.h | 8 --
> arch/arm/plat-omap/include/mach/onenand.h | 29 +++++++
> 9 files changed, 177 insertions(+), 120 deletions(-)
> delete mode 100644 arch/arm/mach-omap2/board-rx51-flash.c
> rename arch/arm/mach-omap2/{board-n800-flash.c => gpmc-onenand.c} (78%)
>
> --
> Signature
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-05-06 18:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 0:25 [PATCH 0/7] Generic gpmc-onenand initialization, v3 Tony Lindgren
2009-05-05 0:25 ` [PATCH 1/7] onenand init: Rename board-n800-flash.c to gpmc-onenand.c Tony Lindgren
2009-05-05 0:26 ` [PATCH 2/7] onenand init: Build gpmc-onenand.o based on CONFIG_MTD_ONENAND_OMAP2 Tony Lindgren
2009-05-05 0:26 ` [PATCH 3/7] onenand init: Rename n800_* functions to gpmc_onenand_* functions Tony Lindgren
2009-05-05 0:26 ` [PATCH 4/7] onenand init: Pass configuration data from board-*.c files Tony Lindgren
2009-05-05 0:26 ` [PATCH 5/7] onenand_init: Allow disabling sync read and write based on flags, v3 Tony Lindgren
2009-05-05 0:26 ` [PATCH 6/7] onenand init: Convert omap3430sdp to use gpmc-onenand Tony Lindgren
2009-05-05 0:27 ` [PATCH 7/7] onenand_init: Clean-up for checkpatch.pl Tony Lindgren
2009-05-06 18:07 ` Tony Lindgren [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=20090506180722.GN5593@atomide.com \
--to=tony@atomide.com \
--cc=adrian.hunter@nokia.com \
--cc=dedekind@infradead.org \
--cc=juha.yrjola@solidboot.com \
--cc=linux-omap@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