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] Few fixes for omaps for v5.8
Date: Wed, 15 Jul 2020 12:08:42 -0700 [thread overview]
Message-ID: <pull-1594840100-132735@atomide.com> (raw)
From: "Tony Lindgren" <tony@atomide.com>
The following changes since commit a352fe371053d047481635da328ea781329c84a4:
Merge branch 'omap-for-v5.8/fixes-rc1' into fixes (2020-06-16 09:26:03 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v5.8/fixes-rc5-signed
for you to fetch changes up to 2a4117df9b436a0e4c79d211284ab2097bcd00dc:
ARM: dts: Fix dcan driver probe failed on am437x platform (2020-07-14 08:03:28 -0700)
----------------------------------------------------------------
Fixes for omaps for v5.8-rc cycle
Few fixes for issues noticed during testing:
- Two DEBUG_ATOMIC_SLEEP fixes for ti-sysc interconnect target module
driver
- A regression fix for ti-sysc no-idle handling that caused issues
compared to earlier platform data based booting
- A fix for memory leak for omap_hwmod_allocate_module
- Fix d_can driver probe for am437x
----------------------------------------------------------------
Chen Tao (1):
ARM: OMAP2+: Fix possible memory leak in omap_hwmod_allocate_module
Tony Lindgren (3):
bus: ti-sysc: Fix wakeirq sleeping function called from invalid context
bus: ti-sysc: Fix sleeping function called from invalid context for RTC quirk
bus: ti-sysc: Do not disable on suspend for no-idle
dillon min (1):
ARM: dts: Fix dcan driver probe failed on am437x platform
arch/arm/boot/dts/am437x-l4.dtsi | 14 ++++++++++----
arch/arm/mach-omap2/omap_hwmod.c | 14 +++++++++++---
drivers/bus/ti-sysc.c | 23 ++++++++++++-----------
3 files changed, 33 insertions(+), 18 deletions(-)
reply other threads:[~2020-07-15 19:09 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=pull-1594840100-132735@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).