netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Gordeev <agordeev@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Linux NICS <linux.nics@intel.com>,
	Shahed Shaikh <shahed.shaikh@qlogic.com>,
	e1000-devel@lists.sourceforge.net,
	Dept-HSGLinuxNICDev@qlogic.com, linux-pci@vger.kernel.org,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Alexander Gordeev <agordeev@redhat.com>,
	netdev@vger.kernel.org
Subject: [PATCH net-next 0/2] Use pci_enable_msix_range() instead of pci_enable_msix()
Date: Fri, 25 Apr 2014 10:06:23 +0200	[thread overview]
Message-ID: <cover.1398412015.git.agordeev@redhat.com> (raw)

Hello,

The series completes converison of network drivers to the new
MSI initialization API.

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.

Thanks!

Cc: Mitch Williams <mitch.a.williams@intel.com>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>
Cc: Shahed Shaikh <shahed.shaikh@qlogic.com>
Cc: Linux NICS <linux.nics@intel.com>
Cc: e1000-devel@lists.sourceforge.net
Cc: Dept-HSGLinuxNICDev@qlogic.com
Cc: netdev@vger.kernel.org
Cc: linux-pci@vger.kernel.org

Alexander Gordeev (2):
  i40evf: Use pci_enable_msix_range() instead of pci_enable_msix()
  qlcnic: Use pci_enable_msix_exact() instead of pci_enable_msix()

 drivers/net/ethernet/intel/i40evf/i40evf_main.c  |   31 ++++++++--------------
 drivers/net/ethernet/qlogic/qlcnic/qlcnic_main.c |    4 +-
 2 files changed, 13 insertions(+), 22 deletions(-)

-- 
1.7.7.6


------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit http://communities.intel.com/community/wired

             reply	other threads:[~2014-04-25  8:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25  8:06 Alexander Gordeev [this message]
2014-04-25  8:06 ` [PATCH net-next 1/2] i40evf: Use pci_enable_msix_range() instead of pci_enable_msix() Alexander Gordeev
2014-04-27 23:30   ` David Miller
2014-04-28  9:50     ` 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=cover.1398412015.git.agordeev@redhat.com \
    --to=agordeev@redhat.com \
    --cc=Dept-HSGLinuxNICDev@qlogic.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=jesse.brandeburg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux.nics@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=shahed.shaikh@qlogic.com \
    /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).