From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [REQUEST PULL] mvebu-fixes-5
Date: Wed, 28 Jan 2015 17:02:31 +0100 [thread overview]
Message-ID: <20150128160231.GA28862@lunn.ch> (raw)
Hi Olof
Here is the 5th set of fixes for 3.19-rc. A single patch, which we need
to fix an issue introduced by a previous fix.
Thanks
Andrew
The following changes since commit 38bdf45f4aa5cb6186d50a29e6cbbd9d486a1519:
bus: mvebu-mbus: fix support of MBus window 13 (2015-01-19 15:40:53 -0600)
are available in the git repository at:
git://git.infradead.org/linux-mvebu.git tags/mvebu-fixes-3.19-5
for you to fetch changes up to 38bdf45f4aa5cb6186d50a29e6cbbd9d486a1519:
bus: mvebu-mbus: fix support of MBus window 13 (2015-01-19 15:40:53 -0600)
----------------------------------------------------------------
The previous fix for Armada XP, disabling I/O coherency, broke Armada
375/38x. Only switch the PL310 to I/O coherent mode if I/O coherency
is enabled.
----------------------------------------------------------------
next reply other threads:[~2015-01-28 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 16:02 Andrew Lunn [this message]
[not found] ` <20150128172902.GA29434@lunn.ch>
2015-01-28 23:01 ` [REQUEST PULL] mvebu-fixes-6 Olof Johansson
2015-01-29 8:10 ` Thomas Petazzoni
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=20150128160231.GA28862@lunn.ch \
--to=andrew@lunn.ch \
--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;
as well as URLs for NNTP newsgroup(s).