mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: agordeev@redhat.com
Cc: linux-kernel@vger.kernel.org, mitch.a.williams@intel.com,
	jesse.brandeburg@intel.com, linux.nics@intel.com,
	e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
	linux-pci@vger.kernel.org, jeffrey.t.kirsher@intel.com
Subject: Re: [PATCH net-next 1/2] i40evf: Use pci_enable_msix_range() instead of pci_enable_msix()
Date: Sun, 27 Apr 2014 19:30:27 -0400 (EDT)	[thread overview]
Message-ID: <20140427.193027.1833767089712636627.davem@davemloft.net> (raw)
In-Reply-To: <110dd7806f49f62272bd960ae8101c9da81a3f01.1398412015.git.agordeev@redhat.com>

From: Alexander Gordeev <agordeev@redhat.com>
Date: Fri, 25 Apr 2014 10:06:24 +0200

> As result of deprecation of MSI-X/MSI enablement functions
> pci_enable_msix() and pci_enable_msi_block() all drivers
> using these two interfaces need to be updated to use the
> new pci_enable_msi_range()  or pci_enable_msi_exact()
> and pci_enable_msix_range() or pci_enable_msix_exact()
> interfaces.
> 
> Signed-off-by: Alexander Gordeev <agordeev@redhat.com>

Jeff, I assume you will take this in via your tree.

Thanks.

  reply	other threads:[~2014-04-27 23:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25  8:06 [PATCH net-next 0/2] " Alexander Gordeev
2014-04-25  8:06 ` [PATCH net-next 1/2] i40evf: " Alexander Gordeev
2014-04-27 23:30   ` David Miller [this message]
2014-04-28  9:50     ` [E1000-devel] " Jeff Kirsher
2014-04-25  8:06 ` [PATCH net-next 2/2] qlcnic: Use pci_enable_msix_exact() " Alexander Gordeev
2014-04-25  8:48   ` Shahed Shaikh
2014-04-25  9:00     ` Alexander Gordeev
2014-04-25  9:02       ` Shahed Shaikh
2014-04-25  9:43         ` [PATCH v2 " Alexander Gordeev
2014-04-25  9:43           ` Shahed Shaikh

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=20140427.193027.1833767089712636627.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=agordeev@redhat.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux.nics@intel.com \
    --cc=mitch.a.williams@intel.com \
    --cc=netdev@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

all inboxes | Powered by JetHome®