From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] one bug fix and other omap fixes for v4.17-rc cycle
Date: Mon, 14 May 2018 01:04:12 -0700 [thread overview]
Message-ID: <20180514080412.e2d7djqhj6yuy5qx@localhost> (raw)
In-Reply-To: <pull-1525967831-865303@atomide.com>
On Thu, May 10, 2018 at 09:00:26AM -0700, Tony Lindgren wrote:
> From: "Tony Lindgren" <tony@atomide.com>
>
> The following changes since commit fb289e3ab10c16834741bb02be740fa9d025fde0:
>
> Merge branch 'omap-for-v4.17/fixes-ti-sysc' into omap-for-v4.17/fixes (2018-04-19 15:48:46 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v17/fixes-rc4
>
> for you to fetch changes up to 41bd6adf3c5d3990d7a67639aff53d54483744fa:
>
> Revert "ARM: dts: logicpd-som-lv: Fix pinmux controller references" (2018-05-07 08:28:17 -0700)
>
> ----------------------------------------------------------------
> Fixes for omap variants for v4.17
>
> This series of patches contains one BUG fix for trace if
> CONFIG_DEBUG_PREEMPT is enabled and a regression fix for omap1 FIQ
> handling on ams-delta. Then there's a dts fix for missing SoC
> compatible on ti81xx board dts files that did matter until we added
> the clkctrl clocks and without that some clocks are now not found.
>
> Then there are two logicpd-som-lv specific dts fixes that fix
> misconfigured pins for WLAN and audio. Turns out we had to revert
> the third one because it caused another regression for USB.
Merged, thanks.
-Olof
prev parent reply other threads:[~2018-05-14 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 16:00 [GIT PULL] one bug fix and other omap fixes for v4.17-rc cycle Tony Lindgren
2018-05-14 8:04 ` Olof Johansson [this message]
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=20180514080412.e2d7djqhj6yuy5qx@localhost \
--to=olof@lixom.net \
--cc=linux-arm-kernel@lists.infradead.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