From: Sathya Perla <sathya.perla@emulex.com>
To: <netdev@vger.kernel.org>
Subject: [PATCH next 0/6] be2net: patch set
Date: Tue, 1 Oct 2013 15:59:55 +0530 [thread overview]
Message-ID: <1380623401-15630-1-git-send-email-sathya.perla@emulex.com> (raw)
Pls apply the following patches to the net-next tree. Thanks.
Sathya Perla (2):
be2net: fix adaptive interrupt coalescing
be2net: add a counter for pkts dropped in xmit path
Vasundhara Volam (4):
be2net: Call be_vf_setup() even when VFs are enbaled from previous
load
be2net: pass if_id for v1 and V2 versions of TX_CREATE cmd
be2net: Create single TXQ on BE3-R 1G ports
be2net: call ENABLE_VF cmd for Skyhawk-R too
drivers/net/ethernet/emulex/benet/be.h | 22 +++-
drivers/net/ethernet/emulex/benet/be_cmds.c | 22 +++--
drivers/net/ethernet/emulex/benet/be_cmds.h | 15 ++--
drivers/net/ethernet/emulex/benet/be_ethtool.c | 33 ++++---
drivers/net/ethernet/emulex/benet/be_main.c | 135 ++++++++++++++----------
5 files changed, 135 insertions(+), 92 deletions(-)
next reply other threads:[~2013-10-01 10:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 10:29 Sathya Perla [this message]
2013-10-01 10:29 ` [PATCH next 1/6] be2net: Call be_vf_setup() even when VFs are enbaled from previous load Sathya Perla
2013-10-01 10:29 ` [PATCH next 2/6] be2net: pass if_id for v1 and V2 versions of TX_CREATE cmd Sathya Perla
2013-10-10 10:53 ` Sathya Perla
2013-10-11 19:02 ` David Miller
2013-10-01 10:29 ` [PATCH next 3/6] be2net: Create single TXQ on BE3-R 1G ports Sathya Perla
2013-10-01 10:29 ` [PATCH next 4/6] be2net: call ENABLE_VF cmd for Skyhawk-R too Sathya Perla
2013-10-01 10:30 ` [PATCH next 5/6] be2net: fix adaptive interrupt coalescing Sathya Perla
2013-10-01 10:30 ` [PATCH next 6/6] be2net: add a counter for pkts dropped in xmit path Sathya Perla
2013-10-01 16:46 ` [PATCH next 0/6] be2net: patch set David Miller
-- strict thread matches above, loose matches on Subject: below --
2013-08-27 11:27 [PATCH next 0/6] be2net " Sathya Perla
2013-08-27 19:57 ` 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=1380623401-15630-1-git-send-email-sathya.perla@emulex.com \
--to=sathya.perla@emulex.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).