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 against v4.5-rc5, fixes more onenand corruption
Date: Wed, 24 Feb 2016 00:10:14 -0800 [thread overview]
Message-ID: <20160224081014.GG30231@localhost> (raw)
In-Reply-To: <20160222213427.GU13417@atomide.com>
On Mon, Feb 22, 2016 at 01:34:28PM -0800, Tony Lindgren wrote:
> The following changes since commit cf26f1137333251f3515dea31f95775b99df0fd5:
>
> ARM: OMAP2+: Fix omap_device for module reload on PM runtime forbid (2016-02-12 08:56:52 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v4.5/fixes-rc5
>
> for you to fetch changes up to 3f315c5b850fa7aff73f50de8e316b98f611a32b:
>
> ARM: OMAP2+: Fix onenand initialization to avoid filesystem corruption (2016-02-22 09:24:10 -0800)
>
> ----------------------------------------------------------------
> Two omap fixes for omaps against v4.5-rc5:
>
> - Yet another fix for n900 onenand to avoid corruption. This time to
> fix the issue of mounting onenand back and forth between the original
> maemo kernel and mainline Linux kernel. And it also seems there will
> be two more fixes coming via the MTD tree as issues were discovered
> also in the onenand driver during testing.
>
> - Revert tps65217 regulator clean up as it breaks MMC for am335x
> variants. The proper way to clean this up is just to rename the
> tps65217.dtsi file into tps65217-am335x.dtsi as a similar setup
> is used on many am335x boards.
Thanks, merged.
-Olof
prev parent reply other threads:[~2016-02-24 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 21:34 [GIT PULL] omap fixes against v4.5-rc5, fixes more onenand corruption Tony Lindgren
2016-02-24 8:10 ` 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=20160224081014.GG30231@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).