linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 5/5] i.MX defconfig updates for 4.18
Date: Fri, 25 May 2018 13:54:00 -0700	[thread overview]
Message-ID: <20180525205400.ix3yguelfeeud7oo@localhost> (raw)
In-Reply-To: <1526828281-14664-5-git-send-email-shawnguo@kernel.org>

On Sun, May 20, 2018 at 10:58:01PM +0800, Shawn Guo wrote:
> The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
> 
>   Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-defconfig-4.18
> 
> for you to fetch changes up to 1049167999fc9a078c5914db9f341a275c2376cb:
> 
>   ARM: imx_v6_v7_defconfig: Select CONFIG_GPIO_MAX732X by default (2018-05-04 17:03:20 +0800)
> 
> ----------------------------------------------------------------
> i.MX defconfig update for 4.18:
>  - Enable i.MX6SLL SoC support.
>  - Build in GPIO_MAX732X support as the GPIO expanders are used on
>    i.MX6 SabreAuto boards.
>  - Enable driver for RN5T618 PMIC and Marvell MWIFIEX support which
>    are found on i.MX6/7 Colibri boards.
>  - Build in OCOTP NVMEM driver for Vybrid (vf610) SoCs.

Merged, thanks!


-Olof

  reply	other threads:[~2018-05-25 20:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-20 14:57 [GIT PULL 1/5] i.MX drivers updates for 4.18 Shawn Guo
2018-05-20 14:57 ` [GIT PULL 2/5] i.MX SoC changes " Shawn Guo
2018-05-25 20:47   ` Olof Johansson
2018-05-20 14:57 ` [GIT PULL 3/5] i.MX device tree updates " Shawn Guo
2018-05-25 20:53   ` Olof Johansson
2018-05-20 14:58 ` [GIT PULL 4/5] Freescale arm64 " Shawn Guo
2018-05-25 20:53   ` Olof Johansson
2018-05-20 14:58 ` [GIT PULL 5/5] i.MX defconfig " Shawn Guo
2018-05-25 20:54   ` Olof Johansson [this message]
2018-05-25 20:47 ` [GIT PULL 1/5] i.MX drivers " 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=20180525205400.ix3yguelfeeud7oo@localhost \
    --to=olof@lixom.net \
    --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 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).