netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Yuval Mintz" <yuvalmin@broadcom.com>
To: davem@davemloft.net, netdev@vger.kernel.org
Cc: eilong@broadcom.com, ariele@broadcom.com,
	"Yuval Mintz" <yuvalmin@broadcom.com>
Subject: [PATCH net-next 0/9] bnx2x: patch series
Date: Mon, 18 Feb 2013 10:16:29 +0200	[thread overview]
Message-ID: <1361175398-12888-1-git-send-email-yuvalmin@broadcom.com> (raw)

Hi Dave,

This patch series contains several SR-IOV related patches -
it allows setting and querying the number of vfs via sysfs,
configuring and querying VFs via iproute2 callbacks and properly
implements for VFs only the ethtool ops which they can safely perform.

In addition, it also contains several small fixes of rare corner-cases.

Please consider applying this patch-series to 'net-next'.

Thanks,
Yuval Mintz

             reply	other threads:[~2013-02-18  9:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18  8:16 Yuval Mintz [this message]
2013-02-18  8:16 ` [PATCH net-next 1/9] bnx2x: Prevent NULL pointer dereference in vlan-mac Yuval Mintz
2013-02-18  8:16 ` [PATCH net-next 2/9] bnx2x: fix vlan-mac memory leak Yuval Mintz
2013-02-18  8:16 ` [PATCH net-next 3/9] bnx2x: handle spurious interrupts Yuval Mintz
2013-02-18 17:39   ` David Miller
2013-02-18  8:16 ` [PATCH net-next 4/9] bnx2x: Set ethtool ops for vfs Yuval Mintz
2013-02-18  8:16 ` [PATCH net-next 5/9] bnx2x: Take chip version from MFW Yuval Mintz
2013-02-18  8:16 ` [PATCH net-next 6/9] bnx2x: Prevent "Unknown MF" print in SF mode Yuval Mintz
2013-02-18  8:16 ` [PATCH net-next 7/9] bnx2x: Add iproute2 support for vfs Yuval Mintz
2013-02-18  8:16 ` [PATCH net-next 8/9] bnx2x: Control number of vfs dynamically Yuval Mintz
2013-02-18  8:16 ` [PATCH net-next 9/9] bnx2x: Get gso_segs from FW Yuval Mintz

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=1361175398-12888-1-git-send-email-yuvalmin@broadcom.com \
    --to=yuvalmin@broadcom.com \
    --cc=ariele@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=eilong@broadcom.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;
as well as URLs for NNTP newsgroup(s).