From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: aik@ozlabs.ru, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-5.0-6 tag
Date: Sat, 23 Feb 2019 23:46:23 +1100 [thread overview]
Message-ID: <87ftsellk0.fsf@concordia.ellerman.id.au> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Linus,
Please pull another powerpc fix for 5.0:
The following changes since commit a58007621be33e9f7c7bed5d5ff8ecb914e1044a:
powerpc/64s: Fix possible corruption on big endian due to pgd/pud_present() (2019-02-17 15:24:45 +1100)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-5.0-6
for you to fetch changes up to 8f5b27347e88b171c755562f0090ce40e514fc00:
powerpc/powernv/sriov: Register IOMMU groups for VFs (2019-02-19 11:51:18 +1100)
- ------------------------------------------------------------------
powerpc fixes for 5.0 #6
One fix for an oops when using SRIOV, introduced by the recent changes to
support compound IOMMU groups.
Thanks to:
Alexey Kardashevskiy.
- ------------------------------------------------------------------
Alexey Kardashevskiy (1):
powerpc/powernv/sriov: Register IOMMU groups for VFs
arch/powerpc/platforms/powernv/pci-ioda.c | 2 ++
arch/powerpc/platforms/powernv/pci.c | 2 ++
2 files changed, 4 insertions(+)
-----BEGIN PGP SIGNATURE-----
iQIcBAEBAgAGBQJccT+TAAoJEFHr6jzI4aWAlYcP/R9XKlvg96FuYEKhJaV3hj1k
QuN3mkaiEia+naAmQrzFgccToUtiMxtQ2Xcg/WryQyOnLKdO1cGuVOrxXSPvTYAE
ESHH7Odd8htt/zzKi/JvHA02puB4u3CmSJu33q6GgDh8LZLyDSjkiQW0tEDB2Oxb
JItN8Q1Swa+On40y2YIQdiKXhhXgHwsH/Mvc5dkNw7N9dCj6kQ908sKFVJ4C7eZI
E2BHnPMOO5hxMHUPI+4CV0J6tKlPoKmJJf8beO9UsrJnMoXO14becJQyqm25jYNg
TPGU3FijIuHolpnBHOJ8EU6c4D8tufC+RDcMprP1o0du8XVekoT3u63LW9xoX8Ff
h3NRDBPeH+D6WtJFl67QTrsVeXaEE23Y2zeYPAoWhBXNzXTJsaiI5dh9N+rYhO/t
t4QLmh2uTVbjHS7KWRVj5m40AlnIJEPGhX8ja8iqRlK2QVbScWmhdbJQRhMa92oe
6/U10sTV9u8Qk6Tf6jRWJdzQJQsHNDx3q1vChmLudQFpJdwc8WzdN2bThgu50rA2
8I1faYBGs2ol3lmjBciRx1KPf5xQUD4NB9K4nmEjG+wlPtLuD1yIl2CGIqapXZoh
brUCNoisrrs7jm6AafauLyid18jZe+uocLiU09OKzpxWZNXulpBwSRYFkjJAr3b0
Q9oTtKpubUI0dhIgOaJp
=lNXB
-----END PGP SIGNATURE-----
next reply other threads:[~2019-02-23 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 12:46 Michael Ellerman [this message]
2019-02-23 19:35 ` [GIT PULL] Please pull powerpc/linux.git powerpc-5.0-6 tag pr-tracker-bot
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=87ftsellk0.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=aik@ozlabs.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.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).