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/3] Renesas driver updates for v6.4 (take two)
Date: Mon, 10 Apr 2023 09:55:27 +0200 [thread overview]
Message-ID: <cover.1681113115.git.geert+renesas@glider.be> (raw)
In-Reply-To: <cover.1681113111.git.geert+renesas@glider.be>
The following changes since commit 2653d5bf1c9d123c0d8b8c1634cf54dacfcfdb52:
soc: renesas: Use "#ifdef" for single-symbol definition checks (2023-03-16 16:58:42 +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-v6.4-tag2
for you to fetch changes up to fc187a46a8e682f0f1167b230792b88de01ceaa0:
soc: renesas: renesas-soc: Release 'chipid' from ioremap() (2023-04-04 10:01:58 +0200)
----------------------------------------------------------------
Renesas driver updates for v6.4 (take two)
- Add "renesas," file contents pattern to MAINTAINERS,
- Fix a small leak on OOM.
----------------------------------------------------------------
Geert Uytterhoeven (1):
MAINTAINERS: renesas: Add "renesas," file contents pattern
Li Yang (1):
soc: renesas: renesas-soc: Release 'chipid' from ioremap()
MAINTAINERS | 1 +
drivers/soc/renesas/renesas-soc.c | 5 ++++-
2 files changed, 5 insertions(+), 1 deletion(-)
next prev parent reply other threads:[~2023-04-10 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 7:55 [GIT PULL 0/3] Renesas SoC updates for v6.4 (take two) Geert Uytterhoeven
2023-04-10 7:55 ` [GIT PULL 1/3] Renesas ARM SoC updates for v6.4 Geert Uytterhoeven
2023-04-10 7:55 ` Geert Uytterhoeven [this message]
2023-04-10 7:55 ` [GIT PULL 3/3] Renesas DTS updates for v6.4 (take two) Geert Uytterhoeven
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.1681113115.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