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 5/6] i.MX arm64 device tree update for 5.2
Date: Mon, 29 Apr 2019 09:27:20 -0700	[thread overview]
Message-ID: <20190429162720.u3lq4mu42l623cmp@localhost> (raw)
In-Reply-To: <20190422082836.3734-5-shawnguo@kernel.org>

On Mon, Apr 22, 2019 at 04:28:35PM +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-dt64-5.2
> 
> for you to fetch changes up to 00c5ce8ac0233fb8975448e720bb1702b36d0725:
> 
>   arm64: dts: lx2160a: add cpu idle support (2019-04-22 10:40:45 +0800)
> 
> ----------------------------------------------------------------
> i.MX arm64 device tree update for 5.2:
>  - Add initial i.MX8MM SoC and EVK board support.
>  - Enable OPP table for cpufreq support on i.MX8MQ, i.MX8QXP and
>    i.MX8MM.
>  - A series from Andrey Smirnov to enable PCIe support for i.MX8MQ.
>  - Add TMU (Thermal Management Unit) device on i.MX8MQ for managing
>    thermal of CPU, GPU, and VPU.
>  - Add SDMA and SAI2 devices for i.MX8MQ SoC and enable wm8524 audio
>    support on EVK board.
>  - Add LPUART, OCOTP and GPU devices for i.MX8MQ SoC.
>  - Add initial i.MX8MQ based Zii Ultra board support
>  - Add SCU general IRQ and watchdog support for i.MX8QXP.
>  - Add audio related devices and PMU for LS1028A.
>  - Enable SATA and cpuidle support for LX2160A.
>  - Other small random updates.

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-29 17:08 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
2019-04-22  8:28 ` [GIT PULL 5/6] i.MX arm64 " Shawn Guo
2019-04-29 16:27   ` Olof Johansson [this message]
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=20190429162720.u3lq4mu42l623cmp@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.