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] omap fixes v4.11-rc cycle
Date: Mon, 13 Mar 2017 15:14:21 -0700 [thread overview]
Message-ID: <20170313221421.GE13064@localhost> (raw)
In-Reply-To: <58bd927a.c5ae540a.8be25.bcd3SMTPIN_ADDED_BROKEN@mx.google.com>
On Mon, Mar 06, 2017 at 08:46:42AM -0800, Tony Lindgren wrote:
> The following changes since commit c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201:
>
> Linux 4.11-rc1 (2017-03-05 12:59:56 -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-rc1-v2
>
> for you to fetch changes up to e24bce8fb4c26bd0d8eca74cbbee1ad049246be3:
>
> Merge tag 'v4.11-rc1' into omap-for-v4.11/fixes (2017-03-06 08:37:53 -0800)
>
> ----------------------------------------------------------------
> Fixes for omaps for v4.11-rc cycle:
>
> - Fix smartreflex platform data regression where I accidentally
> removed legacy platform data still in use
>
> - Fix hypervisor mode for thumb2 kernel
>
> - Fix misplaced tpic2810 to move it to right bus
>
> - Enable INPUT_MOUSEDEV as a loadable module have mice working
>
> - Fix use of gpio-key,wakeup and use wakeup-source instead as
> this accidentally sneaked in during the merge window
>
> - Fix error handling for onenand to properly return error
>
> - Remove legacy gpmc-nand.c that's now dead code, this
> also removes dependency to the MTD tree for further driver
> changes
>
> - Fix device node reference count errors for omap3 and
> related to it also release device nodes after no longer
> needed
Merged.
-Olof
next parent reply other threads:[~2017-03-13 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <58bd927a.c5ae540a.8be25.bcd3SMTPIN_ADDED_BROKEN@mx.google.com>
2017-03-13 22:14 ` Olof Johansson [this message]
2017-03-06 16:46 [GIT PULL] omap fixes v4.11-rc cycle 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=20170313221421.GE13064@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).