From: Olof Johansson <olof@lixom.net>
To: Simon Horman <horms+renesas@verge.net.au>
Cc: arm@kernel.org, linux-renesas-soc@vger.kernel.org,
Kevin Hilman <khilman@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [GIT PULL] Renesas ARM Based SoC Fixes for v5.0
Date: Sat, 12 Jan 2019 22:00:09 -0800 [thread overview]
Message-ID: <20190113060009.5fb4zwcjxapltjzq@localhost> (raw)
In-Reply-To: <cover.1547115367.git.horms+renesas@verge.net.au>
On Thu, Jan 10, 2019 at 11:18:15AM +0100, Simon Horman wrote:
> Hi Olof, Hi Kevin, Hi Arnd,
>
> Please consider these Renesas ARM based SoC fixes for v5.0.
>
>
> The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
>
> Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
>
> are available in the git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-fixes-for-v5.0
>
> for you to fetch changes up to a64597227d0de5610407fcc95dc835745a53f5d0:
>
> soc: renesas: r8a774c0-sysc: Fix initialization order of 3DG-{A,B} (2019-01-07 14:51:51 +0100)
>
> ----------------------------------------------------------------
> Renesas ARM Based SoC Fixes for v5.0
>
> Renesas SoCs:
> * Fix build regressions caused by move of Kconfig symbols
>
> RZ/G2E (r8a774c0) SoC:
> * Correct initialization order of 3DG-{A,B} in SYSC driver
Merged to fixes. Thanks!
-Olof
prev parent reply other threads:[~2019-01-13 6:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 10:18 [GIT PULL] Renesas ARM Based SoC Fixes for v5.0 Simon Horman
2019-01-10 10:18 ` [PATCH 1/2] ARM: shmobile: fix build regressions Simon Horman
2019-01-10 10:18 ` [PATCH 2/2] soc: renesas: r8a774c0-sysc: Fix initialization order of 3DG-{A,B} Simon Horman
2019-01-13 6:00 ` Olof Johansson [this message]
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=20190113060009.5fb4zwcjxapltjzq@localhost \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=horms+renesas@verge.net.au \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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).