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 ARM64 Based SoC Defconfig Updates for v5.2
Date: Fri, 19 Apr 2019 16:33:02 +0200 [thread overview]
Message-ID: <cover.1555683540.git.horms+renesas@verge.net.au> (raw)
Hi Olof, Hi Kevin, Hi Arnd,
Please consider these Renesas ARM64 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-arm64-defconfig-for-v5.2
for you to fetch changes up to 940d1a288a598ee18afa25ee74f4ca124bddd364:
arm64: defconfig: enable RX-8581 config option (2019-03-18 10:32:55 +0100)
----------------------------------------------------------------
Renesas ARM64 Based SoC Defconfig Updates for v5.2
+ Enable support for RX-8571/RX-8581 RTC
----------------------------------------------------------------
Biju Das (1):
arm64: defconfig: enable RX-8581 config option
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-04-19 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 14:33 Simon Horman [this message]
2019-04-19 14:33 ` [PATCH 1/1] arm64: defconfig: enable RX-8581 config option Simon Horman
2019-04-29 6:39 ` [GIT PULL] Renesas ARM64 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.1555683540.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