From: Tony Lindgren <tony@atomide.com>
To: Mike Rapoport <mike@compulab.co.il>
Cc: "Ghorai, Sukumar" <s-ghorai@ti.com>,
Vimal Singh <vimal.newwork@gmail.com>,
"Artem.Bityutskiy@nokia.com" <Artem.Bityutskiy@nokia.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Steve Sakoman <sakoman@gmail.com>
Subject: Re: Upcoming merge window and omap NAND patches
Date: Wed, 5 May 2010 08:11:11 -0700 [thread overview]
Message-ID: <20100505151111.GT29604@atomide.com> (raw)
In-Reply-To: <4BE16AB8.7010308@compulab.co.il>
* Mike Rapoport <mike@compulab.co.il> [100505 05:51]:
> Ghorai,
>
> Ghorai, Sukumar wrote:
> >Tony,
> >I understand your comment/input. And I will work on it.
Great, good to hear.
> >All existing omap3 boards are using same old fashion. So let me see how many board I can test before post the patch. I will update this next week.
>
> I'd be glad to test the patches on CM-T35 if you'd like to.
For this merge window how about just getting rid of OMAP34XX_GPMC_VIRT
in the board-*.c files and move that to gpmc-nand.c?
This may allow adding more board-*.c NAND files without
having to patch all of them later on again.
However, if there are more changes needed to all the board-*.c
files for the NAND platform data, then let's just fix the existing
ones first before adding new ones.
After that, looks like most of the work is to move some of the
GPMC functions from omap2.c to gpmc.c.
Or should they rather be in gpmc-nand.c if they are only used
with NAND connected to GPMC?
Regards,
Tony
prev parent reply other threads:[~2010-05-05 15:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 22:08 Upcoming merge window and omap NAND patches Tony Lindgren
2010-05-05 4:49 ` Artem Bityutskiy
2010-05-05 6:11 ` Vimal Singh
2010-05-05 12:33 ` Ghorai, Sukumar
2010-05-05 12:55 ` Mike Rapoport
2010-05-05 15:11 ` 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=20100505151111.GT29604@atomide.com \
--to=tony@atomide.com \
--cc=Artem.Bityutskiy@nokia.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mike@compulab.co.il \
--cc=s-ghorai@ti.com \
--cc=sakoman@gmail.com \
--cc=vimal.newwork@gmail.com \
/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).