public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Simon Horman <horms+renesas@verge.net.au>
To: arm@kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>, Kevin Hilman <khilman@kernel.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-renesas-soc@vger.kernel.org,
	Olof Johansson <olof@lixom.net>,
	Simon Horman <horms+renesas@verge.net.au>,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Renesas ARM Based SoC Defconfig Updates for v5.2
Date: Fri, 19 Apr 2019 16:34:18 +0200	[thread overview]
Message-ID: <cover.1555654474.git.horms+renesas@verge.net.au> (raw)

Hi Olof, Hi Kevin, Hi Arnd,

Please consider these Renesas ARM based SoC defconfig updates for v5.2.


The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:

  Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)

are available in the git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-arm-defconfig-for-v5.2

for you to fetch changes up to b266731b76d5c33c0f6d781c449e43ad9991fb70:

  ARM: shmobile: Enable USB [EO]HCI HCD PLATFORM support in shmobile_defconfig (2019-04-12 14:16:10 +0200)

----------------------------------------------------------------
Renesas ARM Based SoC Defconfig Updates for v5.2

shmobile and multi_v7 defconfigs
* Enable support for CFI NOR FLASH

shmobile defconfig
* Enable USB [EO]HCI HCD PLATFORM and PHY_RCAR_GEN3_USB2
* Refresh for v5.1-rc1

----------------------------------------------------------------
Biju Das (2):
      ARM: shmobile: Enable PHY_RCAR_GEN3_USB2 in shmobile_defconfig
      ARM: shmobile: Enable USB [EO]HCI HCD PLATFORM support in shmobile_defconfig

Geert Uytterhoeven (3):
      ARM: shmobile: defconfig: Refresh for v5.1-rc1
      ARM: shmobile: defconfig: Enable support for CFI NOR FLASH
      ARM: multi_v7_defconfig: Enable support for CFI NOR FLASH

 arch/arm/configs/multi_v7_defconfig |  4 ++++
 arch/arm/configs/shmobile_defconfig | 13 +++++++++----
 2 files changed, 13 insertions(+), 4 deletions(-)

_______________________________________________
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-19 14:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-19 14:34 Simon Horman [this message]
2019-04-19 14:34 ` [PATCH 1/5] ARM: shmobile: defconfig: Refresh for v5.1-rc1 Simon Horman
2019-04-19 14:34 ` [PATCH 2/5] ARM: shmobile: defconfig: Enable support for CFI NOR FLASH Simon Horman
2019-04-19 14:34 ` [PATCH 3/5] ARM: multi_v7_defconfig: " Simon Horman
2019-04-19 14:34 ` [PATCH 4/5] ARM: shmobile: Enable PHY_RCAR_GEN3_USB2 in shmobile_defconfig Simon Horman
2019-04-23  9:20   ` Geert Uytterhoeven
2019-04-23  9:45     ` Biju Das
2019-04-23 10:28       ` Simon Horman
2019-04-23 10:38         ` Biju Das
2019-04-19 14:34 ` [PATCH 5/5] ARM: shmobile: Enable USB [EO]HCI HCD PLATFORM support " Simon Horman
2019-04-29  6:40 ` [GIT PULL] Renesas ARM Based SoC Defconfig Updates for v5.2 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=cover.1555654474.git.horms+renesas@verge.net.au \
    --to=horms+renesas@verge.net.au \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=khilman@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=olof@lixom.net \
    /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