From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v2 6/6] i.MX defconfig updates for 4.17
Date: Mon, 26 Mar 2018 19:42:32 +0800 [thread overview]
Message-ID: <20180326114230.GD8857@dragon> (raw)
In-Reply-To: <1521113800-16401-6-git-send-email-shawnguo@kernel.org>
Changes for v2:
- Update commit log of patch "ARM: mxs_defconfig: Re-sync defconfig"
to explain the option changes a bit.
The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-defconfig-4.17
for you to fetch changes up to 8bc2c29b550c1c9bb923079cca13c4669572ce6a:
ARM: mxs_defconfig: Re-sync defconfig (2018-03-26 19:23:47 +0800)
----------------------------------------------------------------
i.MX defconfig updates for 4.17:
- Re-sync defconfig files by running savedefconfig.
- Enable generic fsl-asoc-card driver for imx_v4_v5_defconfig.
- Enable MAG3110 magnetometer sensor driver, AC97 and WM8962 codec
driver, DA9062/63 PMIC, RTC and Watchdog support for
imx_v6_v7_defconfig.
----------------------------------------------------------------
Anson Huang (1):
ARM: imx_v6_v7_defconfig: select the CONFIG_CPUFREQ_DT
Fabio Estevam (6):
ARM: imx_v6_v7_defconfig: Enable AC97 codec support
ARM: imx_v6_v7_defconfig: Re-sync defconfig
ARM: imx_v6_v7_defconfig: Select CONFIG_SND_SOC_WM8962 explicitly
ARM: imx_v4_v5_defconfig: Re-sync defconfig
ARM: imx_v4_v5_defconfig: Use the generic fsl-asoc-card driver
ARM: mxs_defconfig: Re-sync defconfig
Marco Franchi (1):
ARM: imx: Update imx_v6_v7_defconfig for mag3110 support
Peng Fan (1):
ARM: imx_v6_v7_defconfig: enable OP-TEE
Stefan Riedmueller (1):
ARM: imx_v6_v7_defconfig: Enable Dialog Semiconductor DA9062 driver
arch/arm/configs/imx_v4_v5_defconfig | 9 +++------
arch/arm/configs/imx_v6_v7_defconfig | 28 +++++++++++++++-------------
arch/arm/configs/mxs_defconfig | 14 ++++----------
3 files changed, 22 insertions(+), 29 deletions(-)
next prev parent reply other threads:[~2018-03-26 11:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 11:36 [GIT PULL 1/6] i.MX drivers updates for 4.17 Shawn Guo
2018-03-15 11:36 ` [GIT PULL 2/6] i.MX SoC changes " Shawn Guo
2018-03-15 15:12 ` Arnd Bergmann
2018-03-16 0:55 ` Shawn Guo
2018-03-15 11:36 ` [GIT PULL 3/6] i.MX device tree updates with new clock " Shawn Guo
2018-03-15 15:03 ` Arnd Bergmann
2018-03-15 11:36 ` [GIT PULL 4/6] i.MX device tree updates " Shawn Guo
2018-03-15 15:08 ` Arnd Bergmann
2018-03-15 16:58 ` Arnd Bergmann
2018-03-15 17:22 ` Fabio Estevam
2018-03-15 18:12 ` Fabio Estevam
2018-03-16 1:30 ` Shawn Guo
2018-03-15 11:36 ` [GIT PULL 5/6] Freescale arm64 " Shawn Guo
2018-03-15 15:29 ` Arnd Bergmann
2018-03-16 1:56 ` Shawn Guo
2018-03-15 11:36 ` [GIT PULL 6/6] i.MX defconfig " Shawn Guo
2018-03-15 15:21 ` Arnd Bergmann
2018-03-15 22:48 ` Fabio Estevam
2018-03-15 23:06 ` Fabio Estevam
2018-03-26 11:42 ` Shawn Guo [this message]
2018-03-27 13:11 ` [GIT PULL v2 " Arnd Bergmann
2018-03-15 15:25 ` [GIT PULL 1/6] i.MX drivers " Arnd Bergmann
2018-03-16 0:47 ` Shawn Guo
2018-03-16 1:22 ` Anson Huang
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=20180326114230.GD8857@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 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).