All of lore.kernel.org
 help / color / mirror / Atom feed
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/4] i.MX device tree updates for 4.15
Date: Mon, 30 Oct 2017 22:46:32 +0800	[thread overview]
Message-ID: <20171030144630.GA6270@dragon> (raw)
In-Reply-To: <CAK8P3a3yb=6gNer8o3yogxOJg43k9KJFQNHhormJP8Rd_f5N+Q@mail.gmail.com>

On Mon, Oct 30, 2017 at 02:09:49PM +0100, Arnd Bergmann wrote:
> On Tue, Oct 24, 2017 at 2:20 PM, Shawn Guo <shawnguo@kernel.org> wrote:
> 
> > i.MX device tree updates for 4.15:
> >  - New board support: i.MX51 ZII RDU1, i.MX53 GE Healthcare PPD, i.MX6
> >    TX modules for MB7 from  Ka-Ro Electronics, i.MX6 Wandboard revd1
> >    variants, i.MX6 LWN DISPLAY5 board, Pistachio i.MX6Q board, i.MX6SX
> >    Vining-2000 board.
> >  - Use the 'vpcie-supply' property for PCIe device for boards
> >    imx6qdl-sabresd, imx6q-novena and imx6q-cm-fx6.
> >  - A series from Jagan Teki to update imx6qdl-icore board with audio,
> >    touch and CAN support.
> >  - Switch to nvmem for accessing OCOTP from tempmon for i.MX6SX and add
> >    tempmon support for i.MX6UL.
> >  - A bunch of patches from Lothar Wa?mann updating Ka-Ro i.MX28, i.MX53
> >    and i.MX6 TX modules.
> >  - Fix DTC warnings in i.MX device trees, dropping leading zeros from
> >    unit address, correcting display nodes notation and display port
> >    names, fixing nodes with unit name and no reg property.
> 
> I got some conflicts against the patch from Rob to drop leading zeros,
> but those were all easy to fix up. I noticed that some of your newly
> added files have new leading zeros, so I removed them during the merge
> as well. Please double-check that the new version in branch next/dt is
> fine.

I compared your next/dt and my imx/dt, and the diff is all about
dropping leading zeros.  So next/dt branch is fine.

Thanks a lot for helping fix it up.  I will pay more attention to
leading zeros for future patch reviewing.

Shawn

  reply	other threads:[~2017-10-30 14:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24 12:20 [GIT PULL 1/4] i.MX SoC changes for 4.15 Shawn Guo
2017-10-24 12:20 ` [GIT PULL 2/4] i.MX device tree updates " Shawn Guo
2017-10-30 13:09   ` Arnd Bergmann
2017-10-30 14:46     ` Shawn Guo [this message]
2017-10-24 12:20 ` [GIT PULL 3/4] Freescale arm64 " Shawn Guo
2017-10-30 13:40   ` Arnd Bergmann
2017-10-24 12:20 ` [GIT PULL 4/4] i.MX defconfig " Shawn Guo
2017-10-30  9:58   ` Arnd Bergmann
2017-10-30 10:22 ` [GIT PULL 1/4] i.MX SoC changes " Arnd Bergmann

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=20171030144630.GA6270@dragon \
    --to=shawnguo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.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.