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: drivers: omap updates for v7.3
Date: Mon, 03 Aug 2026 08:52:29 -0700 [thread overview]
Message-ID: <7hzez3i4le.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/drivers-signed
for you to fetch changes up to 6342de0aed216b6df460b492ddb532b3e0ed16f1:
bus: ti-sysc: Fix /chosen node reference leak (2026-07-06 11:42:48 -0700)
----------------------------------------------------------------
drivers: omap updates for v7.3
- bus: ti-sysc: Fix /chosen node reference leak
----------------------------------------------------------------
Yuho Choi (1):
bus: ti-sysc: Fix /chosen node reference leak
drivers/bus/ti-sysc.c | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
next reply other threads:[~2026-08-03 15:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 15:52 Kevin Hilman [this message]
2026-08-04 20:20 ` [GIT PULL] soc: drivers: omap updates for v7.3 patchwork-bot+linux-soc
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=7hzez3i4le.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