From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Javier Martinez Canillas <martinez.javier@gmail.com>,
Enric Balletbo Serra <eballetbo@gmail.com>,
Pekon Gupta <pekon@ti.com>,
linux-mtd@lists.infradead.org, Jon Hunter <jgchunter@gmail.com>
Subject: Re: [PATCH 0/3] omap2: Assorted GPMC cleanups
Date: Wed, 8 Jan 2014 20:38:16 -0300 [thread overview]
Message-ID: <20140108233815.GC2595@localhost> (raw)
In-Reply-To: <20140108191836.GD31323@atomide.com>
On Wed, Jan 08, 2014 at 11:18:37AM -0800, Tony Lindgren wrote:
> * Ezequiel Garcia <ezequiel.garcia@free-electrons.com> [131027 17:52]:
> > (I'm CCing the MTD list, because GPMC is the memory controller
> > used for NOR, NAND and OneNAND devices).
> >
> > Hi all,
> >
> > Just a small patchset containing two small cleanups and a minor fix
> > for the GPMC memory controller. The first two are cleanups and can
> > be considered as preparation work for the fix.
> >
> > The fix is patch 3/3: "Move legacy GPMC width setting". It makes
> > explicit use of the DT property "gpmc,device-width" and removes the
> > subsequent (and redundant) setting of the GPMC width, based in the
> > NAND bus widht.
>
> Thanks and sorry for the delay. Applying these all into branch
> omap-for-v3.14/fixes-not-urgent.
>
No problem. I'll give this a test/review next week.
Do we still need the board-file (legacy) workaround in this patchset?
I was actually waiting for you to clean-up completely that, before
re-sending the series, without the board-file workaround.
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
--
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
WARNING: multiple messages have this Message-ID (diff)
From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Javier Martinez Canillas <martinez.javier@gmail.com>,
Enric Balletbo Serra <eballetbo@gmail.com>,
Jon Hunter <jgchunter@gmail.com>,
linux-mtd@lists.infradead.org, Pekon Gupta <pekon@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] omap2: Assorted GPMC cleanups
Date: Wed, 8 Jan 2014 20:38:16 -0300 [thread overview]
Message-ID: <20140108233815.GC2595@localhost> (raw)
In-Reply-To: <20140108191836.GD31323@atomide.com>
On Wed, Jan 08, 2014 at 11:18:37AM -0800, Tony Lindgren wrote:
> * Ezequiel Garcia <ezequiel.garcia@free-electrons.com> [131027 17:52]:
> > (I'm CCing the MTD list, because GPMC is the memory controller
> > used for NOR, NAND and OneNAND devices).
> >
> > Hi all,
> >
> > Just a small patchset containing two small cleanups and a minor fix
> > for the GPMC memory controller. The first two are cleanups and can
> > be considered as preparation work for the fix.
> >
> > The fix is patch 3/3: "Move legacy GPMC width setting". It makes
> > explicit use of the DT property "gpmc,device-width" and removes the
> > subsequent (and redundant) setting of the GPMC width, based in the
> > NAND bus widht.
>
> Thanks and sorry for the delay. Applying these all into branch
> omap-for-v3.14/fixes-not-urgent.
>
No problem. I'll give this a test/review next week.
Do we still need the board-file (legacy) workaround in this patchset?
I was actually waiting for you to clean-up completely that, before
re-sending the series, without the board-file workaround.
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] omap2: Assorted GPMC cleanups
Date: Wed, 8 Jan 2014 20:38:16 -0300 [thread overview]
Message-ID: <20140108233815.GC2595@localhost> (raw)
In-Reply-To: <20140108191836.GD31323@atomide.com>
On Wed, Jan 08, 2014 at 11:18:37AM -0800, Tony Lindgren wrote:
> * Ezequiel Garcia <ezequiel.garcia@free-electrons.com> [131027 17:52]:
> > (I'm CCing the MTD list, because GPMC is the memory controller
> > used for NOR, NAND and OneNAND devices).
> >
> > Hi all,
> >
> > Just a small patchset containing two small cleanups and a minor fix
> > for the GPMC memory controller. The first two are cleanups and can
> > be considered as preparation work for the fix.
> >
> > The fix is patch 3/3: "Move legacy GPMC width setting". It makes
> > explicit use of the DT property "gpmc,device-width" and removes the
> > subsequent (and redundant) setting of the GPMC width, based in the
> > NAND bus widht.
>
> Thanks and sorry for the delay. Applying these all into branch
> omap-for-v3.14/fixes-not-urgent.
>
No problem. I'll give this a test/review next week.
Do we still need the board-file (legacy) workaround in this patchset?
I was actually waiting for you to clean-up completely that, before
re-sending the series, without the board-file workaround.
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-01-08 23:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 0:51 [PATCH 0/3] omap2: Assorted GPMC cleanups Ezequiel Garcia
2013-10-28 0:51 ` Ezequiel Garcia
2013-10-28 0:51 ` Ezequiel Garcia
2013-10-28 0:51 ` [PATCH 1/3] omap2: gpmc: Move initialization outside the gpmc_t condition Ezequiel Garcia
2013-10-28 0:51 ` Ezequiel Garcia
2013-10-28 0:51 ` Ezequiel Garcia
2013-10-28 0:51 ` [PATCH 2/3] omap2: gpmc: Introduce gpmc_set_legacy() Ezequiel Garcia
2013-10-28 0:51 ` Ezequiel Garcia
2013-10-28 0:51 ` Ezequiel Garcia
2013-10-28 0:51 ` [PATCH 3/3] omap2: gpmc: Move legacy GPMC width setting Ezequiel Garcia
2013-10-28 0:51 ` Ezequiel Garcia
2013-10-28 0:51 ` Ezequiel Garcia
2013-11-06 19:16 ` [PATCH 0/3] omap2: Assorted GPMC cleanups Ezequiel Garcia
2013-11-06 19:16 ` Ezequiel Garcia
2013-11-06 19:16 ` Ezequiel Garcia
2014-01-08 19:18 ` Tony Lindgren
2014-01-08 19:18 ` Tony Lindgren
2014-01-08 19:18 ` Tony Lindgren
2014-01-08 23:38 ` Ezequiel Garcia [this message]
2014-01-08 23:38 ` Ezequiel Garcia
2014-01-08 23:38 ` Ezequiel Garcia
2014-01-08 23:40 ` Tony Lindgren
2014-01-08 23:40 ` Tony Lindgren
2014-01-08 23:40 ` 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=20140108233815.GC2595@localhost \
--to=ezequiel.garcia@free-electrons.com \
--cc=eballetbo@gmail.com \
--cc=jgchunter@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=martinez.javier@gmail.com \
--cc=pekon@ti.com \
--cc=tony@atomide.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.