From: Rusty Russell <rusty@rustcorp.com.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
LKML <linux-kernel@vger.kernel.org>,
virtualization@lists.linux-foundation.org,
Fabian Frederick <fabf@skynet.be>,
Benoit Taine <benoit.taine@lip6.fr>,
Amit Shah <amit.shah@redhat.com>
Subject: [PULL] virtio-next
Date: Mon, 11 Aug 2014 11:58:50 +0930 [thread overview]
Message-ID: <87vbpzahel.fsf@rustcorp.com.au> (raw)
The following changes since commit 15ba2236f3556fc01b9ca91394465152b5ea74b6:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2014-07-21 22:46:01 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux.git tags/virtio-next-for-linus
for you to fetch changes up to eeec626366ffe558fc3d5685bd2b49a962acf57d:
Revert "hwrng: virtio - ensure reads happen after successful probe" (2014-07-27 21:07:20 +0930)
----------------------------------------------------------------
Cheers,
Rusty.
----------------------------------------------------------------
Amit Shah (4):
virtio: rng: remove unused struct element
virtio: rng: re-arrange struct elements for better packing
virtio: rng: delay hwrng_register() till driver is ready
Revert "hwrng: virtio - ensure reads happen after successful probe"
Benoit Taine (1):
virtio: Replace DEFINE_PCI_DEVICE_TABLE macro use
Fabian Frederick (1):
virtio: console: remove unnecessary null test before debugfs_remove_recursive
drivers/char/hw_random/core.c | 6 ------
drivers/char/hw_random/virtio-rng.c | 39 ++++++++++++++++---------------------
drivers/char/virtio_console.c | 6 ++----
drivers/virtio/virtio_pci.c | 2 +-
4 files changed, 20 insertions(+), 33 deletions(-)
next reply other threads:[~2014-08-11 2:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 2:28 Rusty Russell [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-02-18 5:15 [PULL] virtio-next Rusty Russell
2013-07-01 0:55 Rusty Russell
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=87vbpzahel.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=amit.shah@redhat.com \
--cc=arnd@arndb.de \
--cc=benoit.taine@lip6.fr \
--cc=fabf@skynet.be \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=virtualization@lists.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).