DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>, DPDK <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/4] bnxt patch series
Date: Thu, 29 Sep 2016 18:32:59 +0100	[thread overview]
Message-ID: <027f4f71-f93e-c4b9-f63c-34348960e183@intel.com> (raw)
In-Reply-To: <20160929170328.GA52117@C02PT1RBG8WP.aus.broadcom.com>

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

  reply	other threads:[~2016-09-29 17:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-29 17:03 Ajit Khaparde
2016-09-29 17:32 ` Ferruh Yigit [this message]
2016-10-13  9:56   ` Bruce Richardson

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=027f4f71-f93e-c4b9-f63c-34348960e183@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.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).