From: Alex Williamson <alex.williamson@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
kvm <kvm@vger.kernel.org>,
fengguang.wu@intel.com, julia.lawall@lip6.fr,
jiang.liu@huawei.com, Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [GIT PULL v2] VFIO updates for v3.8
Date: Tue, 11 Dec 2012 21:02:21 -0700 [thread overview]
Message-ID: <1355284941.3224.196.camel@bling.home> (raw)
Hi Linus,
Take 2 using the same commits as in Stephen's next tree, please note the
new tag below. There's a merge with v3.7 in my for-linus branch of the
below tree, not that you should need it. Thanks,
Alex
The following changes since commit 1afa471706963643ceeda7cbbe9c605a1e883d53:
Merge tag 'mmc-fixes-for-3.7' of git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc (2012-12-07 09:15:20 -0800)
are available in the git repository at:
git://github.com/awilliam/linux-vfio.git tags/vfio-for-v3.8-v2
for you to fetch changes up to 9a92c5091a42c565ede818fdf204c4f60004d0d8:
vfio-pci: Enable device before attempting reset (2012-12-07 13:43:51 -0700)
----------------------------------------------------------------
vfio pull for v3.8
----------------------------------------------------------------
Alex Williamson (2):
vfio-pci: Re-order device reset
vfio-pci: Enable device before attempting reset
Fengguang Wu (1):
vfio: simplify kmalloc+copy_from_user to memdup_user
Jiang Liu (3):
VFIO: unregister IOMMU notifier on error recovery path
VFIO: use ACCESS_ONCE() to guard access to dev->driver
VFIO: fix out of order labels for error recovery in vfio_pci_init()
drivers/vfio/pci/vfio_pci.c | 83 +++++++++++++++++++++++++--------------------
drivers/vfio/vfio.c | 34 +++++++++----------
2 files changed, 64 insertions(+), 53 deletions(-)
next reply other threads:[~2012-12-12 4:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 4:02 Alex Williamson [this message]
2012-12-17 16:30 ` [GIT PULL v2] VFIO updates for v3.8 Alex Williamson
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=1355284941.3224.196.camel@bling.home \
--to=alex.williamson@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=jiang.liu@huawei.com \
--cc=julia.lawall@lip6.fr \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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).