From: Alex Williamson <alex.williamson@redhat.com>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>
Cc: kvm@vger.kernel.org, bhelgaas@google.com, linux-pci@vger.kernel.org
Subject: Re: [PATCH 0/4] VFIO Misc fixes
Date: Fri, 30 May 2014 15:06:42 -0600 [thread overview]
Message-ID: <1401484002.9207.1.camel@ul30vt.home> (raw)
In-Reply-To: <1400535439.3289.284.camel@ul30vt.home>
On Mon, 2014-05-19 at 15:37 -0600, Alex Williamson wrote:
> On Mon, 2014-05-19 at 13:01 +1000, Gavin Shan wrote:
> > Changelog
> > =========
> > v1 -> v2:
> > * Change the comments and commit log in PATCH[4/4] (Alex).
> > * Export 2 MSI relevant functions (Alex).
> > v2 -> v3:
> > * Add missed header file in PATCH[4/4].
>
> Please specify the version in the Subject for all patches.
>
> It would probably be a good idea to separate this series. Patches 2 & 3
> stand on their own. Send them that way so we can actually get them in.
> Patch 4 is dependent on Patch 1, so send them as a series.
I'm going to go ahead and grab patches 2 & 3 here because I don't want
to see them miss another kernel. Thanks,
Alex
prev parent reply other threads:[~2014-05-30 21:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 3:01 [PATCH 0/4] VFIO Misc fixes Gavin Shan
2014-05-19 3:01 ` [PATCH 1/4] PCI: Export MSI message relevant functions Gavin Shan
2014-05-22 5:10 ` Gavin Shan
2014-09-04 22:57 ` Bjorn Helgaas
2014-09-05 0:15 ` Gavin Shan
2014-05-19 3:01 ` [PATCH 2/4] drivers/vfio: Rework offsetofend() Gavin Shan
2014-05-19 3:01 ` [PATCH 3/4] drivers/vfio/pci: Fix wrong MSI interrupt count Gavin Shan
2014-05-19 3:01 ` [PATCH 4/4] vfio/pci: Restore MSIx message prior to enabling Gavin Shan
2014-05-30 22:12 ` Bjorn Helgaas
2014-05-31 11:42 ` Gavin Shan
2014-06-02 16:57 ` Bjorn Helgaas
2014-06-05 5:51 ` Gavin Shan
2014-09-10 8:13 ` Gavin Shan
2014-09-26 3:19 ` Gavin Shan
2014-09-26 3:46 ` Alex Williamson
2014-09-27 5:33 ` Gavin Shan
2014-05-19 21:37 ` [PATCH 0/4] VFIO Misc fixes Alex Williamson
2014-05-30 21:06 ` Alex Williamson [this message]
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=1401484002.9207.1.camel@ul30vt.home \
--to=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-pci@vger.kernel.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).