From: Shawn Guo <shawnguo@kernel.org>
To: Oliver Graute <oliver.graute@kococonnector.com>
Cc: "Neil Armstrong" <narmstrong@baylibre.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Andrey Smirnov" <andrew.smirnov@gmail.com>,
"Aisheng Dong" <aisheng.dong@nxp.com>,
"Sébastien Szymanski" <sebastien.szymanski@armadeus.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] dt-bindings: arm: fsl: Document Variscite i.MX6q devicetree
Date: Mon, 28 Oct 2019 21:25:36 +0800 [thread overview]
Message-ID: <20191028132534.GM16985@dragon> (raw)
In-Reply-To: <20191028120519.GA4147@optiplex>
On Mon, Oct 28, 2019 at 12:07:32PM +0000, Oliver Graute wrote:
> On 28/10/19, Shawn Guo wrote:
> > On Thu, Oct 24, 2019 at 09:22:37AM +0000, Oliver Graute wrote:
> > > Document the Variscite i.MX6qdl board devicetree binding
> > > already supported:
> > >
> > > - variscite,dt6customboard
> > >
> > > Signed-off-by: Oliver Graute <oliver.graute@kococonnector.com>
> > > Cc: Shawn Guo <shawnguo@kernel.org>
> > > Cc: Neil Armstrong <narmstrong@baylibre.com>
> >
> > Please organise it into the patch series, where it's being used.
>
> I think this was just forgotten on this commit:
Ah, sorry, missed the fact. Applied, thanks.
Shawn
>
> commit 26b7784b29e90da926ff3c290107f7e78c807314
> Author: Neil Armstrong <narmstrong@baylibre.com>
> Date: Mon Dec 4 10:21:09 2017 +0100
>
> ARM: dts: imx6q: Add Variscite DART-MX6 Carrier-board support
>
> This patch adds support for the i.MX6 Quad variant of the Variscite DART-MX6
> SoM Carrier-Board.
prev parent reply other threads:[~2019-10-28 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 9:22 [PATCH v1] dt-bindings: arm: fsl: Document Variscite i.MX6q devicetree Oliver Graute
2019-10-28 11:38 ` Shawn Guo
2019-10-28 12:07 ` Oliver Graute
2019-10-28 13:25 ` Shawn Guo [this message]
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=20191028132534.GM16985@dragon \
--to=shawnguo@kernel.org \
--cc=aisheng.dong@nxp.com \
--cc=andrew.smirnov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mark.rutland@arm.com \
--cc=narmstrong@baylibre.com \
--cc=oliver.graute@kococonnector.com \
--cc=robh+dt@kernel.org \
--cc=sebastien.szymanski@armadeus.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.