From: Geert Uytterhoeven <geert+renesas@glider.be>
To: arm-soc <arm@kernel.org>, soc <soc@kernel.org>
Cc: Magnus Damm <magnus.damm@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-renesas-soc@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [GIT PULL 2/2] Renesas driver updates for v5.18 (take two)
Date: Fri, 25 Feb 2022 11:24:34 +0100 [thread overview]
Message-ID: <cover.1645784470.git.geert+renesas@glider.be> (raw)
In-Reply-To: <cover.1645784465.git.geert+renesas@glider.be>
The following changes since commit cb5508e47e60b85ac033edd8c52245ad51360eb4:
soc: renesas: Add support for reading product revision for RZ/G2L family (2022-02-08 09:43:06 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git tags/renesas-drivers-for-v5.18-tag2
for you to fetch changes up to 088659ad2a830124407edc38da278010c95bcc96:
soc: renesas: Kconfig: Introduce ARCH_RZG2L config option (2022-02-24 13:53:25 +0100)
----------------------------------------------------------------
Renesas driver updates for v5.18 (take two)
- RZ/G2L and RZ/V2L need PM and PM_GENERIC_DOMAINS,
- Introduce ARCH_RZG2L family for RZ/G2L, RZ/G2LC, RZ/G2UL and RZ/V2L
SoCs.
----------------------------------------------------------------
Lad Prabhakar (2):
soc: renesas: Kconfig: Explicitly select PM and PM_GENERIC_DOMAINS configs
soc: renesas: Kconfig: Introduce ARCH_RZG2L config option
drivers/soc/renesas/Kconfig | 7 +++++++
1 file changed, 7 insertions(+)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-02-25 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 10:24 [GIT PULL 0/2] Renesas SoC updates for v5.18 (take two) Geert Uytterhoeven
2022-02-25 10:24 ` [GIT PULL 1/2] Renesas ARM DT " Geert Uytterhoeven
2022-02-25 10:24 ` Geert Uytterhoeven [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=cover.1645784470.git.geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=soc@kernel.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).