Netdev List
 help / color / mirror / Atom feed
From: Yuval Mintz <yuvalmin@broadcom.com>
To: <davem@davemloft.net>, <netdev@vger.kernel.org>
Cc: <ariele@broadcom.com>
Subject: [PATCH net-next 0/9] bnx2x: Enhancements & semantic changes series
Date: Mon, 10 Feb 2014 17:16:53 +0200	[thread overview]
Message-ID: <1392045422-5437-1-git-send-email-yuvalmin@broadcom.com> (raw)

Hi Dave,

This patch series contains several semantic (or mostly semantic) patches,
as well as adding support for packet aggregations on the receive path
of windows VMs and updating bnx2x to the new FW recently accepted upstream.

Please consider applying these patches to `net-next'.

Thanks,
Yuval Mintz

             reply	other threads:[~2014-02-10 15:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 15:16 Yuval Mintz [this message]
2014-02-10 15:16 ` [PATCH net-next 1/9] bnx2x: [Debug] change verbosity of some prints Yuval Mintz
2014-02-10 15:16 ` [PATCH net-next 2/9] bnx2x: Remove unused iov code Yuval Mintz
2014-02-10 15:16 ` [PATCH net-next 3/9] bnx2x: Remove unnecessary internal mem config Yuval Mintz
2014-02-10 15:16 ` [PATCH net-next 4/9] bnx2x: Semantic Validate vlan/mac changes Yuval Mintz
2014-02-10 15:16 ` [PATCH net-next 5/9] bnx2x: Add support in PF driver for RSC Yuval Mintz
2014-02-10 15:16 ` [PATCH net-next 6/9] bnx2x: Revise IOV vlan/mac validation Yuval Mintz
2014-02-10 15:17 ` [PATCH net-next 7/9] bnx2x: Fix bnx2x_panic_dump for VFs Yuval Mintz
2014-02-10 15:17 ` [PATCH net-next 8/9] bnx2x: (semantic) revise scheduling of sp_rtnl Yuval Mintz
2014-02-10 15:17 ` [PATCH net-next 9/9] bnx2x: utilize FW 7.8.19 Yuval Mintz
2014-02-10 22:32 ` [PATCH net-next 0/9] bnx2x: Enhancements & semantic changes series David Miller
  -- strict thread matches above, loose matches on Subject: below --
2014-02-12 16:19 Yuval Mintz
2014-02-13  0:16 ` David Miller

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=1392045422-5437-1-git-send-email-yuvalmin@broadcom.com \
    --to=yuvalmin@broadcom.com \
    --cc=ariele@broadcom.com \
    --cc=davem@davemloft.net \
    --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