From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH 0/4] bnxt patch series Date: Thu, 29 Sep 2016 18:32:59 +0100 Message-ID: <027f4f71-f93e-c4b9-f63c-34348960e183@intel.com> References: <20160929170328.GA52117@C02PT1RBG8WP.aus.broadcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit To: Ajit Khaparde , DPDK Return-path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id F227B19F5 for ; Thu, 29 Sep 2016 19:33:01 +0200 (CEST) In-Reply-To: <20160929170328.GA52117@C02PT1RBG8WP.aus.broadcom.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 9/29/2016 6:03 PM, Ajit Khaparde wrote: > Please consider applying this patch series. > This series is expected to be applied over the previous patchset > once it is accepted. > Depends on: [v2,15/15] bnxt: Update struct definitions to use the 1.5.1 > HWRM API > http://dpdk.org/dev/patchwork/patch/16154/ > > Ajit Khaparde (4): > testpmd: Add support to configure 25G and 50G speeds > bnxt: Fix a segfault encountered during KNI exit > bnxt: Add support for Async Link Notification > bnxt: Update the Broadcom PMD driver documentation > > app/test-pmd/cmdline.c | 14 ++- > doc/guides/nics/bnxt.rst | 18 ++-- > doc/guides/testpmd_app_ug/testpmd_funcs.rst | 2 +- > drivers/net/bnxt/Makefile | 1 + > drivers/net/bnxt/bnxt.h | 7 +- > drivers/net/bnxt/bnxt_cpr.c | 21 ++-- > drivers/net/bnxt/bnxt_ethdev.c | 148 +++++++++++++++++++++----- > drivers/net/bnxt/bnxt_hwrm.c | 93 +++++++++-------- > drivers/net/bnxt/bnxt_irq.c | 156 ++++++++++++++++++++++++++++ > drivers/net/bnxt/bnxt_irq.h | 51 +++++++++ > 10 files changed, 409 insertions(+), 102 deletions(-) > create mode 100644 drivers/net/bnxt/bnxt_irq.c > create mode 100644 drivers/net/bnxt/bnxt_irq.h > Hi Ajit, Can you please prefer sending patches in a threaded manner, that helps keeping them organized. All other patches in patchset should be as reply to first patch of patchset (and if it is a patchset, first patch is most probably a cover-letter): [0/x] ... [1/x] ... .... [x/x] ... if you use git send-email, it does this automatically for you (with proper configuration), more details on: http://dpdk.org/doc/guides/contributing/patches.html#sending-patches Thanks, ferruh