From: Tony Lindgren <tony@atomide.com>
To: soc@kernel.org
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, arm@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] three fixes for omaps for v5.4
Date: Wed, 23 Oct 2019 09:39:57 -0700 [thread overview]
Message-ID: <pull-1571848757-282222@atomide.com> (raw)
From: "Tony Lindgren" <tony@atomide.com>
The following changes since commit 17a9e5bbbfe5a5a6356e47cdc1c1656e1e5e1f62:
Merge tag 'wlcore-fix' into fixes (2019-10-11 09:15:35 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v5.4/fixes-rc4-signed
for you to fetch changes up to 6aed5a0e0f56213cc5e4bff674fb42e997f30df7:
Merge branch 'watchdog-fix' into fixes (2019-10-18 08:47:39 -0700)
----------------------------------------------------------------
Three fixes for omaps for v5.4-rc cycle
Two regression fixes for omap3 iommu. I missed applying two omap3
related iommu pdata quirks patches earlier because the kbuild test
robot produced errors on them for missing dependencies.
Fix ti-sysc interconnect target module driver handling for watchdog
quirk. I must have tested this earlier only with watchdog service
running, but clearly it does not do what it needs to do.
----------------------------------------------------------------
Suman Anna (2):
ARM: OMAP2+: Plug in device_enable/idle ops for IOMMUs
ARM: OMAP2+: Add pdata for OMAP3 ISP IOMMU
Tony Lindgren (2):
bus: ti-sysc: Fix watchdog quirk handling
Merge branch 'watchdog-fix' into fixes
arch/arm/mach-omap2/pdata-quirks.c | 11 +++++++++++
drivers/bus/ti-sysc.c | 18 ++++++++++++++----
2 files changed, 25 insertions(+), 4 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2019-10-23 16: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=pull-1571848757-282222@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).