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] ARM: omap: soc updates for v6.20
Date: Thu, 22 Jan 2026 10:40:42 -0800 [thread overview]
Message-ID: <7h343x7aol.fsf@baylibre.com> (raw)
The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:
Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap.git tags/omap-for-v6.20/soc-signed
for you to fetch changes up to dc717e24deb4e626f4ad4896dd722815ef32311a:
ARM: omap1: drop unused Kconfig symbol (2026-01-05 12:11:02 -0800)
----------------------------------------------------------------
ARM: omap: soc updates for v6.20
----------------------------------------------------------------
Randy Dunlap (1):
ARM: omap1: drop unused Kconfig symbol
Wentao Liang (1):
ARM: omap2: Fix reference count leaks in omap_control_init()
arch/arm/mach-omap1/Kconfig | 1 -
arch/arm/mach-omap2/control.c | 14 ++++++++++----
2 files changed, 10 insertions(+), 5 deletions(-)
reply other threads:[~2026-01-22 18:40 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=7h343x7aol.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