From: Tony Lindgren <tony@atomide.com>
To: soc@kernel.org
Cc: arm@kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Tony Lindgren" <tony@atomide.com>
Subject: [GIT PULL] Fixes for omaps
Date: Fri, 8 Dec 2023 14:17:15 +0200 [thread overview]
Message-ID: <pull-1702037799-781982@atomide.com> (raw)
From: "Tony Lindgren" <tony@atomide.com>
The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86:
Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v6.7/fixes-signed
for you to fetch changes up to c72b9c33ef9695ad7ce7a6eb39a9df8a01b70796:
ARM: OMAP2+: Fix null pointer dereference and memory leak in omap_soc_device_init (2023-11-30 13:57:00 +0200)
----------------------------------------------------------------
Fixes for omaps
A few fixes for omaps:
- A regression fix for ti-sysc interconnect target module driver to not access
registers after reset if srst_udelay quirk is needed
- DRA7 L3 NoC node register size fix
----------------------------------------------------------------
Andrew Davis (1):
ARM: dts: dra7: Fix DRA7 L3 NoC node register size
Kunwu Chan (1):
ARM: OMAP2+: Fix null pointer dereference and memory leak in omap_soc_device_init
Tony Lindgren (1):
bus: ti-sysc: Flush posted write only after srst_udelay
arch/arm/boot/dts/ti/omap/dra7.dtsi | 2 +-
arch/arm/mach-omap2/id.c | 5 +++++
drivers/bus/ti-sysc.c | 18 ++++++++++++++----
3 files changed, 20 insertions(+), 5 deletions(-)
next reply other threads:[~2023-12-08 12:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 12:17 Tony Lindgren [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-18 5:19 [GIT PULL] Fixes for omaps Tony Lindgren
2023-08-16 4:02 Tony Lindgren
2022-04-21 12:15 Tony Lindgren
2022-02-23 8:55 Tony Lindgren
2022-01-10 7:55 Tony Lindgren
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=pull-1702037799-781982@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--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).