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: Sat, 22 Feb 2014 09:58:10 +0100 [thread overview]
Message-ID: <530866A2.7080804@redhat.com> (raw)
In-Reply-To: <20140222085030.GA26794@dhcp-26-207.brq.redhat.com>
Il 22/02/2014 09:50, Alexander Gordeev ha scritto:
> Commit d158fc7 ("Merge tag 'pci-v3.14-fixes-1'") in Linus's tree has it.
>
> pci_enable_msix() is going to be removed once all drivers updated with
> new interface.
>
>> > 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?
> So it is already in.
It is not, because maintainer branches are not rebased. KVM development
is based on 3.14-rc1, and will not get that commit until the first 3.15
pull request is sent to Linux.
No big deal, I'll include this patch in a second 3.15 pull request.
Paolo
next prev parent reply other threads:[~2014-02-22 8:58 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
2014-02-22 8:50 ` Alexander Gordeev
2014-02-22 8:58 ` Paolo Bonzini [this message]
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=530866A2.7080804@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.