From: Artem Bityutskiy <dedekind1@gmail.com>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: Huang Shijie <b32955@freescale.com>,
linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] mtd: gpmi: add device tree support for mx6q and mx28
Date: Thu, 03 May 2012 13:54:45 +0300 [thread overview]
Message-ID: <1336042485.13013.41.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20120502144008.GF2194@S2101-09.ap.freescale.net>
[-- Attachment #1: Type: text/plain, Size: 663 bytes --]
On Wed, 2012-05-02 at 22:40 +0800, Shawn Guo wrote:
> On Wed, May 02, 2012 at 02:13:28PM +0800, Huang Shijie wrote:
> > add gpmi support for mx6q.
> > add DT support to mx6q and mx28.
> >
> > Signed-off-by: Huang Shijie <b32955@freescale.com>
>
> Hi Artem,
>
> As the patch heavily depends on mxs device tree branch, I think it will
> be easier to have it go through arm-soc tree. If you agree, can you
> please give your ack if the patch looks fine to you?
I do not mind if it goes via the arm-soc tree. I cannot really review
this patch - it is too big, I think it should be split on smaller
chunks.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: dedekind1@gmail.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] mtd: gpmi: add device tree support for mx6q and mx28
Date: Thu, 03 May 2012 13:54:45 +0300 [thread overview]
Message-ID: <1336042485.13013.41.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20120502144008.GF2194@S2101-09.ap.freescale.net>
On Wed, 2012-05-02 at 22:40 +0800, Shawn Guo wrote:
> On Wed, May 02, 2012 at 02:13:28PM +0800, Huang Shijie wrote:
> > add gpmi support for mx6q.
> > add DT support to mx6q and mx28.
> >
> > Signed-off-by: Huang Shijie <b32955@freescale.com>
>
> Hi Artem,
>
> As the patch heavily depends on mxs device tree branch, I think it will
> be easier to have it go through arm-soc tree. If you agree, can you
> please give your ack if the patch looks fine to you?
I do not mind if it goes via the arm-soc tree. I cannot really review
this patch - it is too big, I think it should be split on smaller
chunks.
--
Best Regards,
Artem Bityutskiy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120503/11b13754/attachment.sig>
next prev parent reply other threads:[~2012-05-03 10:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 6:13 [PATCH v3] mtd: gpmi: add device tree support for mx6q and mx28 Huang Shijie
2012-05-02 6:13 ` Huang Shijie
2012-05-02 14:40 ` Shawn Guo
2012-05-02 14:40 ` Shawn Guo
2012-05-03 10:54 ` Artem Bityutskiy [this message]
2012-05-03 10:54 ` Artem Bityutskiy
2012-05-03 12:38 ` Shawn Guo
2012-05-03 12:38 ` Shawn Guo
2012-05-03 14:14 ` Huang Shijie
2012-05-03 14:14 ` Huang Shijie
2012-05-03 14:23 ` Shawn Guo
2012-05-03 14:23 ` Shawn Guo
2012-05-04 2:14 ` Huang Shijie
2012-05-04 2:14 ` Huang Shijie
2012-05-04 2:28 ` Shawn Guo
2012-05-04 2:28 ` Shawn Guo
2012-05-04 2:39 ` Huang Shijie
2012-05-04 2:39 ` Huang Shijie
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=1336042485.13013.41.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=b32955@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=shawn.guo@linaro.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 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.