From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Gordeev <agordeev@redhat.com>
Cc: linux-kernel@vger.kernel.org, Gleb Natapov <gleb@kernel.org>,
kvm@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v2] kvm: Use pci_enable_msix_exact() instead of pci_enable_msix()
Date: Fri, 21 Feb 2014 22:36:25 +0100 [thread overview]
Message-ID: <5307C6D9.4030503@redhat.com> (raw)
In-Reply-To: <20140221185620.GA18725@dhcp-26-207.brq.redhat.com>
Il 21/02/2014 19:56, Alexander Gordeev ha scritto:
> On Fri, Feb 21, 2014 at 06:11:29PM +0100, Paolo Bonzini wrote:
>> It's okay, but it's not clear to me whether I should include this
>> patch or someone else will. :)
>
> Please, include it.
And where do I get pci_enable_msix_exact? When will pci_enable_msix
disappear?
So, do I have to pull something (which I'd rather not, since pulling the
wrong thing in a submaintainer tree will make Linus angry), or should I
do it in the next merge window after pci_enable_msix_exact gets in?
All in all, it seems much simpler to me if the linux-pci tree just
includes the whole patch series with my Acked-by.
Paolo
> Thanks!
>
>> Paolo
>
next prev parent reply other threads:[~2014-02-21 21:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 10:15 [PATCH] kvm: Use pci_enable_msix_range() instead of pci_enable_msix() Alexander Gordeev
2014-02-19 13:24 ` Paolo Bonzini
2014-02-21 17:04 ` Alexander Gordeev
2014-02-21 17:05 ` [PATCH v2] kvm: Use pci_enable_msix_exact() " Alexander Gordeev
2014-02-21 17:11 ` Paolo Bonzini
2014-02-21 18:56 ` Alexander Gordeev
2014-02-21 21:36 ` Paolo Bonzini [this message]
2014-02-22 8:50 ` Alexander Gordeev
2014-02-22 8:58 ` Paolo Bonzini
2014-04-21 13:38 ` Alexander Gordeev
2014-04-24 20:45 ` Paolo Bonzini
2014-04-28 9:13 ` Paolo Bonzini
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=5307C6D9.4030503@redhat.com \
--to=pbonzini@redhat.com \
--cc=agordeev@redhat.com \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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).