From: Olof Johansson <olof@lixom.net>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, arm@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 1/5] non-urgent omap fixes for v4.11 merge window
Date: Sun, 29 Jan 2017 17:15:00 -0800 [thread overview]
Message-ID: <20170130011500.GV3133@localhost> (raw)
In-Reply-To: <58879773.4111630a.b973d.9b1cSMTPIN_ADDED_BROKEN@mx.google.com>
On Tue, Jan 24, 2017 at 10:05:14AM -0800, Tony Lindgren wrote:
> The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77:
>
> Linux 4.10-rc1 (2016-12-25 16:13:08 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.11/fixes-not-urgent-signed
>
> for you to fetch changes up to 631af44c10f9430163296626c6134db16a4f51fb:
>
> ARM: OMAP3: Fix SoC detection of OMAP36/37 Family (2017-01-20 10:13:06 -0800)
>
> ----------------------------------------------------------------
> Non-urgent fixes for omaps for v4.11 merge window. These all are
> fixes for things that have never worked or have been broken for
> a long time and nobody noticed:
>
> - Fix omap3 off mode pull defines
>
> - Allow multiple pdata quirks instead of just one
>
> - Fix am335x and dm814x scm syscon to probe children too
>
> - Fix compatible for ti81xx to allow use with 8250_omap as well
>
> - Fix 8250_omap on omap5 by adding HWMOD_SWSUP_SIDLE_ACT flag
>
> - Fix SoC detection for omap36/37 SoCs
Merged, thanks!
-Olof
next parent reply other threads:[~2017-01-30 1:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <58879773.4111630a.b973d.9b1cSMTPIN_ADDED_BROKEN@mx.google.com>
2017-01-30 1:15 ` Olof Johansson [this message]
2017-01-24 18:05 [GIT PULL 1/5] non-urgent omap fixes for v4.11 merge window 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=20170130011500.GV3133@localhost \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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).