All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Stefan Agner <stefan@agner.ch>, Li Yang <leoyang.li@nxp.com>,
	arm@kernel.org, linux-imx@nxp.com, kernel@pengutronix.de,
	Fabio Estevam <festevam@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 4/6] i.MX arm device tree update for 5.2
Date: Sun, 28 Apr 2019 12:51:35 -0700	[thread overview]
Message-ID: <20190428195135.dbbwxqivmno3bg6d@localhost> (raw)
In-Reply-To: <20190423020804.GD16166@dragon>

On Tue, Apr 23, 2019 at 10:08:06AM +0800, Shawn Guo wrote:
> On Mon, Apr 22, 2019 at 04:28:34PM +0800, Shawn Guo wrote:
> > The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
> > 
> >   Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
> > 
> > are available in the Git repository at:
> > 
> >   git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-dt-5.2
> > 
> > for you to fetch changes up to 2ea5c9b28fab2f34a0ac5d9b3d17216dd35d3162:
> > 
> >   ARM: dts: vf610-zii-dev-rev-b: Specify CS as GPIO_ACTIVE_LOW in spi0 (2019-04-22 09:16:15 +0800)
> 
> Hi Arnd, Olof,
> 
> I updated the tag to include the missing patch that adds #io-channel-cells
> in ADC nodes.  Otherwise, we have DTC warning below from ZII i.MX7 RPU2
> board support.
> 
>   arch/arm/boot/dts/imx7d-zii-rpu2.dts:46.12-50.4: Warning (io_channels_property): /iio-hwmon: Missing property '#io-channel-cells' in node /soc/aips-bus@30400000/adc@30610000 or bad phandle (referred from io-channels[0]) 
> 
> Shawn
> 
> 
> The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
> 
>   Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-dt-5.2
> 
> for you to fetch changes up to 4171797ff78fa1f351b890e18411b7959b506149:
> 
>   ARM: dts: imx7s: Specify #io-channel-cells in ADC nodes (2019-04-23 09:48:26 +0800)

Merged, thanks!


-Olof

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-04-28 20:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-22  8:28 [GIT PULL 1/6] i.MX drivers change for 5.2 Shawn Guo
2019-04-22  8:28 ` [GIT PULL 2/6] i.MX SoC update " Shawn Guo
2019-04-29 16:26   ` Olof Johansson
2019-04-22  8:28 ` [GIT PULL 3/6] i.MX DT bindings " Shawn Guo
2019-04-23  2:03   ` Shawn Guo
2019-04-28 19:50     ` Olof Johansson
2019-04-22  8:28 ` [GIT PULL 4/6] i.MX arm device tree " Shawn Guo
2019-04-23  2:08   ` Shawn Guo
2019-04-28 19:51     ` Olof Johansson [this message]
2019-04-22  8:28 ` [GIT PULL 5/6] i.MX arm64 " Shawn Guo
2019-04-29 16:27   ` Olof Johansson
2019-04-22  8:28 ` [GIT PULL 6/6] i.MX defconfig " Shawn Guo
2019-04-29 16:29   ` Olof Johansson
2019-04-30  2:26     ` Shawn Guo
2019-04-30  2:31       ` Fabio Estevam
2019-04-30 21:18       ` Leonard Crestez
2019-05-01  0:41         ` Shawn Guo
2019-05-03 14:12           ` Leonard Crestez
2019-05-04 13:28     ` Shawn Guo
2019-04-29 16:25 ` [GIT PULL 1/6] i.MX drivers change " Olof Johansson

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=20190428195135.dbbwxqivmno3bg6d@localhost \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=shawnguo@kernel.org \
    --cc=stefan@agner.ch \
    /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.