From: Tony Lindgren <tony@atomide.com>
To: vimal singh <vimalsingh@ti.com>
Cc: dedekind@infradead.org, linux-omap@vger.kernel.org,
adrian.hunter@nokia.com, Tony Lindgren <tony@atommide.com>
Subject: Re: [PATCH 1/4] onenand init: Rename board-n800-flash.c to gpmc-onenand.c
Date: Thu, 30 Apr 2009 07:03:37 -0700 [thread overview]
Message-ID: <20090430140336.GC12986@atomide.com> (raw)
In-Reply-To: <40106.192.168.10.89.1241073191.squirrel@dbdmail.itg.ti.com>
* vimal singh <vimalsingh@ti.com> [090429 23:33]:
> 'gpmc-onenand.c' is still confusing name. This is not going to used in
> all boards anyway.
Why do you think this cannot be used for all boards?
The GPMC timings are totally based on the onenand chip features.
Regards,
Tony
> On Thu, Apr 30, 2009 at 3:20 AM, Tony Lindgren <tony@atomide.com> wrote:
> > Rename board-n800-flash.c to gpmc-onenand.c.
> >
> > Signed-off-by: Tony Lindgren <tony@atommide.com>
> > ---
> > arch/arm/mach-omap2/Makefile | 4 ++--
> > arch/arm/mach-omap2/gpmc-onenand.c | 0
> > 2 files changed, 2 insertions(+), 2 deletions(-)
> > rename arch/arm/mach-omap2/{board-n800-flash.c => gpmc-onenand.c} (100%)
> >
> > diff --git a/arch/arm/mach-omap2/Makefile b/arch/arm/mach-omap2/Makefile
> > index 76acefa..9127a94 100644
> > --- a/arch/arm/mach-omap2/Makefile
> > +++ b/arch/arm/mach-omap2/Makefile
> > @@ -55,14 +55,14 @@ obj-$(CONFIG_MACH_OMAP_LDP) += board-ldp.o \
> > obj-$(CONFIG_MACH_OMAP_APOLLON) += board-apollon.o \
> > board-apollon-mmc.o \
> > board-apollon-keys.o
> > -obj-$(CONFIG_MACH_NOKIA_N800) += board-n800.o board-n800-flash.o \
> > +obj-$(CONFIG_MACH_NOKIA_N800) += board-n800.o gpmc-onenand.o \
> > board-n800-mmc.o board-n800-bt.o \
> > board-n800-usb.o \
> > board-n800-dsp.o \
> > board-n800-camera.o
> > obj-$(CONFIG_MACH_NOKIA_N810) += board-n810.o
> > obj-$(CONFIG_MACH_NOKIA_RX51) += board-rx51.o \
> > - board-n800-flash.o \
> > + gpmc-onenand.o \
> > board-rx51-flash.o \
> > board-rx51-sdram.o \
> > board-rx51-video.o \
> > diff --git a/arch/arm/mach-omap2/board-n800-flash.c
> b/arch/arm/mach-omap2/gpmc-onenand.c
> > similarity index 100%
> > rename from arch/arm/mach-omap2/board-n800-flash.c
> > rename to arch/arm/mach-omap2/gpmc-onenand.c
> >
> > --
> > 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
> >
>
>
>
> --
> ---
> Regards,
> \/ | |\/| /-\ |_
>
>
next prev parent reply other threads:[~2009-04-30 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 6:33 [PATCH 1/4] onenand init: Rename board-n800-flash.c to gpmc-onenand.c vimal singh
2009-04-30 14:03 ` Tony Lindgren [this message]
2009-04-30 18:53 ` [PATCH] onenand_init: Allow disabling sync read and write based on flags (Re: [PATCH 1/4] onenand init: Rename board-n800-flash.c to gpmc-onenand.c) Tony Lindgren
2009-04-30 18:59 ` [PATCH] onenand init: Convert omap3430sdp to use gpmc-onenand (Re: [PATCH] onenand_init: Allow disabling sync read and write based on flags (Re: [PATCH 1/4] onenand init: Rename board-n800-flash.c to gpmc-onenand.c)) Tony Lindgren
2009-05-01 17:38 ` [PATCH] onenand_init: Allow disabling sync read and write based on flags, v2 (Re: [PATCH 1/4] onenand init: Rename board-n800-flash.c to gpmc-onenand.c) Tony Lindgren
2009-05-04 8:27 ` [PATCH] onenand_init: Allow disabling sync read and write based on flags " Adrian Hunter
2009-05-04 17:39 ` [PATCH] onenand_init: Allow disabling sync read and write based on flags, v3 Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2009-04-29 21:49 [PATCH 0/4] Generic gpmc-onenand initialization, v2 Tony Lindgren
2009-04-29 21:50 ` [PATCH 1/4] onenand init: Rename board-n800-flash.c to gpmc-onenand.c Tony Lindgren
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=20090430140336.GC12986@atomide.com \
--to=tony@atomide.com \
--cc=adrian.hunter@nokia.com \
--cc=dedekind@infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atommide.com \
--cc=vimalsingh@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.