From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linus.walleij@linaro.org, Liviu.Dudau@arm.com,
linux-kernel@vger.kernel.org,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
bhelgaas@google.com
Subject: [git pull] Please pull mpe.git for-linus branch (for powerpc)
Date: Thu, 16 Oct 2014 17:13:24 +1100 [thread overview]
Message-ID: <1413440004.20705.7.camel@concordia> (raw)
[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]
Hi Linus,
There was a bit of a misunderstanding between us and the ARM guys in the device
tree PCI code, which is breaking virtio on powerpc. This is the minimal fix
until we can sort it out properly.
cheers
The following changes since commit 0429fbc0bdc297d64188483ba029a23773ae07b0:
Merge branch 'for-3.18-consistent-ops' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu (2014-10-15 07:48:18 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mpe/linux.git for-linus
for you to fetch changes up to aeba3731b150188685225b510886f1370d8814de:
powerpc/pci: Fix IO space breakage after of_pci_range_to_resource() change (2014-10-16 14:19:07 +1100)
----------------------------------------------------------------
Michael Ellerman (1):
powerpc/pci: Fix IO space breakage after of_pci_range_to_resource() change
arch/powerpc/kernel/pci-common.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2014-10-16 6:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 6:13 Michael Ellerman [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-27 5:53 [git pull] Please pull mpe.git for-linus branch (for powerpc) Michael Ellerman
2014-11-19 5:21 Michael Ellerman
2014-11-04 4:40 Michael Ellerman
2014-10-29 8:52 Michael Ellerman
2014-10-20 9:15 Michael Ellerman
2014-10-10 22:46 Michael Ellerman
2014-09-11 4:42 Michael Ellerman
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=1413440004.20705.7.camel@concordia \
--to=mpe@ellerman.id.au \
--cc=Liviu.Dudau@arm.com \
--cc=bhelgaas@google.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=torvalds@linux-foundation.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).