From: Shawn Guo <shawnguo@kernel.org>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: Fabio Estevam <fabio.estevam@nxp.com>,
Nikita Yushchenko <nikita.yoush@cogentembedded.com>,
Lucas Stach <l.stach@pengutronix.de>,
Chris Healy <cphealy@gmail.com>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/4] ARM: dts: imx6qdl-zii-rdu2: Populate RAVE SP EEPROM nodes
Date: Sun, 1 Jul 2018 21:48:55 +0800 [thread overview]
Message-ID: <20180701134854.GV4348@dragon> (raw)
In-Reply-To: <CAHQ1cqHpX_nz+xyyPg30kXsn2oTp2BBzk-qpCi3z3kezg1PTWg@mail.gmail.com>
On Wed, Jun 27, 2018 at 09:39:37PM -0700, Andrey Smirnov wrote:
> On Wed, Jun 27, 2018 at 9:24 PM Andrey Smirnov <andrew.smirnov@gmail.com> wrote:
> >
> > ZII's RDU1s come with two EEPROMs attached to RAVE SP. Add
>
> Ugh, the description should read RDU2, not RDU1. Will fix in v2,
> tomorrow. Sorry about that.
I fixed it up and applied the series.
Shawn
next prev parent reply other threads:[~2018-07-01 13:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 4:24 [PATCH 0/4] RDU1/2 latest supported RAVE SP nodes Andrey Smirnov
2018-06-28 4:24 ` [PATCH 1/4] ARM: dts: imx51-zii-rdu1: Populate RAVE SP EEPROM nodes Andrey Smirnov
2018-06-28 4:24 ` [PATCH 2/4] ARM: dts: imx6qdl-zii-rdu2: " Andrey Smirnov
2018-06-28 4:39 ` Andrey Smirnov
2018-07-01 13:48 ` Shawn Guo [this message]
2018-06-28 4:24 ` [PATCH 3/4] ARM: dts: imx6qdl-zii-rdu2: Populate RAVE SP backlight node Andrey Smirnov
2018-06-28 4:24 ` [PATCH 4/4] ARM: dts: imx6qdl-zii-rdu2: Populate RAVE SP power button node Andrey Smirnov
2018-06-28 9:53 ` [PATCH 0/4] RDU1/2 latest supported RAVE SP nodes Lucas Stach
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=20180701134854.GV4348@dragon \
--to=shawnguo@kernel.org \
--cc=andrew.smirnov@gmail.com \
--cc=cphealy@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nikita.yoush@cogentembedded.com \
--cc=robh+dt@kernel.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 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).