From: Kevin Hilman <khilman@baylibre.com>
To: soc@lists.linux.dev
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] soc: OMAP2 updates for v7.3
Date: Mon, 03 Aug 2026 08:51:53 -0700 [thread overview]
Message-ID: <7h5x1rjj6u.fsf@baylibre.com> (raw)
The following changes since commit dc59e4fea9d83f03bad6bddf3fa2e52491777482:
Linux 7.2-rc1 (2026-06-28 12:01:31 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap.git tags/omap-for-v7.3/soc-signed
for you to fetch changes up to 76103814279724e5c98b1c16a730f56ebede9f74:
ARM: OMAP2+: Fix OF node reference leaks in omap_hwmod (2026-06-29 13:13:52 -0700)
----------------------------------------------------------------
soc: OMAP2 updates for v7.3
- minor fixes
----------------------------------------------------------------
Mithil Bavishi (1):
ARM: OMAP2+: Add CFI type for omap4_finish_suspend
Yuho Choi (1):
ARM: OMAP2+: Fix OF node reference leaks in omap_hwmod
arch/arm/mach-omap2/omap_hwmod.c | 26 ++++++++++++++++++--------
arch/arm/mach-omap2/sleep44xx.S | 5 +++--
2 files changed, 21 insertions(+), 10 deletions(-)
reply other threads:[~2026-08-03 15:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7h5x1rjj6u.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=soc@lists.linux.dev \
/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