From: David Miller <davem@davemloft.net>
To: sriharsha.basavapatna@broadcom.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/6] be2net: patch-set
Date: Wed, 07 Sep 2016 22:47:17 -0700 (PDT) [thread overview]
Message-ID: <20160907.224717.2076352680190588868.davem@davemloft.net> (raw)
In-Reply-To: <20160907142754.13284-1-sriharsha.basavapatna@broadcom.com>
From: Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
Date: Wed, 7 Sep 2016 19:57:48 +0530
> The following patch set contains an error recovery feature and a few
> bug fixes. Please consider applying this to the net-next tree. Thanks.
>
> Patch-1 Supports HW error recovery in Skyhawk/BEx adapters
> Patch-2 Fixes driver unload to issue function reset FW command
> Patch-3 Avoids issuing GET_EXT_FAT_CAPABILITIES command for VFs
> Patch-4 Avoids redundant addition of mac address in HW
> Patch-5 Fixes mac address collision in some configurations
> Patch-6 Updates driver version
Series applied, thanks.
prev parent reply other threads:[~2016-09-08 6:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 14:27 [PATCH net-next 0/6] be2net: patch-set Sriharsha Basavapatna
2016-09-07 14:27 ` [PATCH net-next 1/6] be2net: Support UE recovery in BEx/Skyhawk adapters Sriharsha Basavapatna
2016-09-07 14:27 ` [PATCH net-next 2/6] be2net: Issue COMMON_RESET_FUNCTION cmd during driver unload Sriharsha Basavapatna
2016-09-07 14:27 ` [PATCH net-next 3/6] be2net: Add privilege level check for OPCODE_COMMON_GET_EXT_FAT_CAPABILITIES SLI cmd Sriharsha Basavapatna
2016-09-07 14:27 ` [PATCH net-next 4/6] be2net: Avoid redundant addition of mac address in HW Sriharsha Basavapatna
2016-09-07 14:27 ` [PATCH net-next 5/6] be2net: Fix mac address collision in some configurations Sriharsha Basavapatna
2016-09-07 14:27 ` [PATCH net-next 6/6] be2net: Update the driver version to 11.1.0.0 Sriharsha Basavapatna
2016-09-08 5:47 ` David Miller [this message]
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=20160907.224717.2076352680190588868.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sriharsha.basavapatna@broadcom.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).