linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: kraxel@redhat.com, Rusty Russell <rusty@rustcorp.com.au>
Subject: [PATCH 00/05] virtio_pci modern driver fixups
Date: Tue, 20 Jan 2015 18:25:05 +0200	[thread overview]
Message-ID: <1421771093-1589-1-git-send-email-mst@redhat.com> (raw)

These are fixup patches for virtio pci modern.
I think it's best to simply squash them in the
appropriate original patches - rebase -i and then apply,
then rebase -i --autosquash to do this automatically.

You can also find how your branch looks with patches applied
but before the rebase -i --autosquash in my tree:
	git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git virtio-next
or after rebase -i --autosquash:
	git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-next

Last patch is a cleanup, does not have to be squashed.

Or if it's all too much bother, I can repost the whole series after fixups.

Michael S. Tsirkin (15):
  fixup! virtio_pci: modern driver
  fixup! virtio_pci: modern driver
  fixup! virtio_pci: macros for PCI layout offsets
  fixup! virtio_pci: add module param to force legacy mode
  virtio_pci_modern: drop an unused function

-- 
MST


             reply	other threads:[~2015-01-20 16:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 16:25 Michael S. Tsirkin [this message]
2015-01-20 16:25 ` [PATCH 01/05] fixup! virtio_pci: modern driver Michael S. Tsirkin
2015-01-20 16:25 ` [PATCH 02/05] " Michael S. Tsirkin
2015-01-20 16:25 ` [PATCH 03/05] fixup! virtio_pci: macros for PCI layout offsets Michael S. Tsirkin
2015-01-20 16:25 ` [PATCH 04/05] fixup! virtio_pci: add module param to force legacy mode Michael S. Tsirkin
2015-01-20 16:25 ` [PATCH 05/05] virtio_pci_modern: drop an unused function Michael S. Tsirkin
2015-01-21  6:00 ` [PATCH 00/05] virtio_pci modern driver fixups Rusty Russell
2015-01-21 13:40 ` Gerd Hoffmann

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=1421771093-1589-1-git-send-email-mst@redhat.com \
    --to=mst@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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).