From: Artem Bityutskiy <dedekind1@gmail.com>
To: Vimal Singh <vimal.newwork@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org,
Linux MTD <linux-mtd@lists.infradead.org>,
vimal singh <vimalsingh@ti.com>
Subject: Re: [PATCH-v6 0/4] OMAP: Adding flash support to SDP, ZOOM2 and LDP boards
Date: Fri, 27 Nov 2009 09:37:21 +0200 [thread overview]
Message-ID: <1259307441.7518.6.camel@localhost> (raw)
In-Reply-To: <ce9ab5790911240725x29b8bd6eq9f9c7a8b21c6786e@mail.gmail.com>
On Tue, 2009-11-24 at 20:55 +0530, Vimal Singh wrote:
> On Tue, Nov 24, 2009 at 8:36 PM, Artem Bityutskiy <dedekind1@gmail.com> wrote:
> > On Thu, 2009-11-19 at 19:38 +0530, Vimal Singh wrote:
> >> Here is the v6 of this patch series. I am cc'ing mtd list too this time.
> >>
> >>
> >> From 8bc97108cf9c78216f1ea5407ccbd900e6b63dc2 Mon Sep 17 00:00:00 2001
> >> From: Vimal Singh <vimalsingh@ti.com>
> >> Date: Thu, 19 Nov 2009 19:28:11 +0530
> >>
> >> This patch series adds flash support for NAND (in sdp, zoom and ldp),
> >> OneNAND and NOR (in sdp)
> >>
> >> Tested on Zoom2 and 3430SDP
> >>
> >> Vimal Singh (4):
> >> [PATCH-v6 1/4] OMAP2/3: Add support for flash on SDP boards
> >> [PATCH-v6 2/4] OMAP3: Add support for NAND on ZOOM/LDP boards
> >> [PATCH-v6 3/4] OMAP: Zoom2: Enable NAND and JFFS2 support in defconfig
> >> [PATCH-v6 4/4] OMAP: 3430SDP: Enable NAND in defconfig
> >
> > Is it possible to separate the MTD and OMAP parts?
>
> 1st patch does migration of gpmc low level calls from omap2.c to gpmc-nand.c.
> I am not sure how we can have separate patches for this.
Ok. It looks like you intend to merge this stuff via linux-omap, which
seems right.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Vimal Singh <vimal.newwork@gmail.com>
Cc: linux-omap@vger.kernel.org,
Linux MTD <linux-mtd@lists.infradead.org>,
Tony Lindgren <tony@atomide.com>, vimal singh <vimalsingh@ti.com>
Subject: Re: [PATCH-v6 0/4] OMAP: Adding flash support to SDP, ZOOM2 and LDP boards
Date: Fri, 27 Nov 2009 09:37:21 +0200 [thread overview]
Message-ID: <1259307441.7518.6.camel@localhost> (raw)
In-Reply-To: <ce9ab5790911240725x29b8bd6eq9f9c7a8b21c6786e@mail.gmail.com>
On Tue, 2009-11-24 at 20:55 +0530, Vimal Singh wrote:
> On Tue, Nov 24, 2009 at 8:36 PM, Artem Bityutskiy <dedekind1@gmail.com> wrote:
> > On Thu, 2009-11-19 at 19:38 +0530, Vimal Singh wrote:
> >> Here is the v6 of this patch series. I am cc'ing mtd list too this time.
> >>
> >>
> >> From 8bc97108cf9c78216f1ea5407ccbd900e6b63dc2 Mon Sep 17 00:00:00 2001
> >> From: Vimal Singh <vimalsingh@ti.com>
> >> Date: Thu, 19 Nov 2009 19:28:11 +0530
> >>
> >> This patch series adds flash support for NAND (in sdp, zoom and ldp),
> >> OneNAND and NOR (in sdp)
> >>
> >> Tested on Zoom2 and 3430SDP
> >>
> >> Vimal Singh (4):
> >> [PATCH-v6 1/4] OMAP2/3: Add support for flash on SDP boards
> >> [PATCH-v6 2/4] OMAP3: Add support for NAND on ZOOM/LDP boards
> >> [PATCH-v6 3/4] OMAP: Zoom2: Enable NAND and JFFS2 support in defconfig
> >> [PATCH-v6 4/4] OMAP: 3430SDP: Enable NAND in defconfig
> >
> > Is it possible to separate the MTD and OMAP parts?
>
> 1st patch does migration of gpmc low level calls from omap2.c to gpmc-nand.c.
> I am not sure how we can have separate patches for this.
Ok. It looks like you intend to merge this stuff via linux-omap, which
seems right.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
--
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
next prev parent reply other threads:[~2009-11-27 7:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 11:31 [PATCH-v3 0/3] OMAP: Adding flash support to SDP, ZOOM2 and LDP boards vimal singh
2009-09-26 2:57 ` vimal singh
2009-10-26 12:07 ` [PATCH-v4 0/4] " Vimal Singh
2009-11-04 11:28 ` Vimal Singh
2009-11-09 20:52 ` Tony Lindgren
2009-11-10 10:01 ` [PATCH-v5 " Vimal Singh
2009-11-19 14:08 ` [PATCH-v6 " Vimal Singh
2009-11-19 14:11 ` Vimal Singh
2009-11-19 14:22 ` Nishanth Menon
2009-11-19 14:22 ` Nishanth Menon
2009-11-19 14:26 ` Vimal Singh
2009-11-19 14:26 ` Vimal Singh
2009-11-24 15:06 ` Artem Bityutskiy
2009-11-24 15:06 ` Artem Bityutskiy
2009-11-24 15:25 ` Vimal Singh
2009-11-24 15:25 ` Vimal Singh
2009-11-27 7:37 ` Artem Bityutskiy [this message]
2009-11-27 7:37 ` Artem Bityutskiy
2009-12-02 14:09 ` Vimal Singh
2009-12-02 14:09 ` Vimal Singh
2009-12-03 20:19 ` Tony Lindgren
2009-12-03 20:19 ` 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=1259307441.7518.6.camel@localhost \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--cc=vimal.newwork@gmail.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.