From: Shawn Guo <shawnguo@kernel.org>
To: Jagan Teki <jagan@openedev.com>
Cc: devicetree@vger.kernel.org, Matteo Lisi <matteo.lisi@engicam.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jagan Teki <jteki@openedev.com>,
Michael Trimarchi <michael@amarulasolutions.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v7 0/5] ARM: dts: imx6q: Add Engicam i.CoreM6 dts
Date: Fri, 21 Oct 2016 09:35:46 +0800 [thread overview]
Message-ID: <20161021013546.GF30578@tiger> (raw)
In-Reply-To: <CAD6G_RQyLtgJw=djPTmY5t7UVwzuZpj0xM0HjchLQjq7P5hMOg@mail.gmail.com>
On Tue, Oct 18, 2016 at 05:30:28PM +0530, Jagan Teki wrote:
> Hi Shawn,
>
> On Fri, Oct 14, 2016 at 2:57 PM, Jagan Teki <jteki@openedev.com> wrote:
> > This is series add dts support for Engicam I.Core M6 qdl modules. just
> > rebased on top of linux-next of previous set[1].
> >
> > [1] http://www.spinics.net/lists/kernel/msg2358233.html
> >
> > Jagan Teki (5):
> > ARM: dts: imx6q: Add Engicam i.CoreM6 Quad/Dual initial support
> > ARM: dts: imx6q: Add Engicam i.CoreM6 DualLite/Solo initial support
> > ARM: dts: imx6qdl-icore: Add usbhost support
> > ARM: dts: imx6qdl-icore: Add usbotg support
> > ARM: dts: imx6qdl-icore: Add FEC support
> >
> > arch/arm/boot/dts/Makefile | 2 +
> > arch/arm/boot/dts/imx6dl-icore.dts | 59 ++++++++
> > arch/arm/boot/dts/imx6q-icore.dts | 59 ++++++++
> > arch/arm/boot/dts/imx6qdl-icore.dtsi | 271 +++++++++++++++++++++++++++++++++++
> > 4 files changed, 391 insertions(+)
> > create mode 100644 arch/arm/boot/dts/imx6dl-icore.dts
> > create mode 100644 arch/arm/boot/dts/imx6q-icore.dts
> > create mode 100644 arch/arm/boot/dts/imx6qdl-icore.dtsi
>
> Can you pick this series?
Sorry for the delay. The first two patches look good, and I had a
couple of small comments on the other 3. Also, for the initial board
support submission like this, you do not need to split it per device
support. That said, please squash the series into one patch when
resending.
Shawn
next prev parent reply other threads:[~2016-10-21 1:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 9:27 [PATCH v7 0/5] ARM: dts: imx6q: Add Engicam i.CoreM6 dts Jagan Teki
[not found] ` <1476437243-13297-1-git-send-email-jteki-oRp2ZoJdM/RWk0Htik3J/w@public.gmane.org>
2016-10-14 9:27 ` [PATCH v7 1/5] ARM: dts: imx6q: Add Engicam i.CoreM6 Quad/Dual initial support Jagan Teki
2016-10-14 9:27 ` [PATCH v7 2/5] ARM: dts: imx6q: Add Engicam i.CoreM6 DualLite/Solo " Jagan Teki
2016-10-14 9:27 ` [PATCH v7 5/5] ARM: dts: imx6qdl-icore: Add FEC support Jagan Teki
2016-10-21 1:31 ` Shawn Guo
2016-10-14 9:27 ` [PATCH v7 3/5] ARM: dts: imx6qdl-icore: Add usbhost support Jagan Teki
2016-10-21 1:21 ` Shawn Guo
2016-10-14 9:27 ` [PATCH v7 4/5] ARM: dts: imx6qdl-icore: Add usbotg support Jagan Teki
[not found] ` <1476437243-13297-5-git-send-email-jteki-oRp2ZoJdM/RWk0Htik3J/w@public.gmane.org>
2016-10-21 1:25 ` Shawn Guo
2016-10-18 12:00 ` [PATCH v7 0/5] ARM: dts: imx6q: Add Engicam i.CoreM6 dts Jagan Teki
2016-10-21 1:35 ` Shawn Guo [this message]
2016-10-21 7:55 ` Jagan Teki
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=20161021013546.GF30578@tiger \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jagan@openedev.com \
--cc=jteki@openedev.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matteo.lisi@engicam.com \
--cc=michael@amarulasolutions.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).