DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 3/3] doc: update release notes for Broadcom PMD
Date: Wed, 20 Nov 2019 08:55:57 -0800	[thread overview]
Message-ID: <CACZ4nhs0DbdNPNpz0q3hct_f3_-NJ9cJhR6HjV83w37P1B6x+g@mail.gmail.com> (raw)
In-Reply-To: <ed94ac54-7765-4550-c2e3-d63f580c322b@intel.com>

On Wed, Nov 20, 2019 at 1:45 AM Ferruh Yigit <ferruh.yigit@intel.com> wrote:

> On 11/20/2019 9:34 AM, Ferruh Yigit wrote:
> > On 11/19/2019 6:56 PM, Ajit Khaparde wrote:
> >> Update release doc briefly describing updates to bnxt PMD for
> >> 19.11 release.
> >>
> >> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> >> ---
> >>  doc/guides/rel_notes/release_19_11.rst | 10 ++++++++++
> >>  1 file changed, 10 insertions(+)
> >>
> >> diff --git a/doc/guides/rel_notes/release_19_11.rst
> b/doc/guides/rel_notes/release_19_11.rst
> >> index 21be600ab..5d70e213e 100644
> >> --- a/doc/guides/rel_notes/release_19_11.rst
> >> +++ b/doc/guides/rel_notes/release_19_11.rst
> >> @@ -201,6 +201,16 @@ New Features
> >>    * Enabled zero copy between application mempools and UMEM by
> enabling the
> >>      XDP_UMEM_UNALIGNED_CHUNKS UMEM flag.
> >>
> >> +* **Updated Broadcom bnxt driver.**
> >> +
> >> +  Updated Broadcom bnxt driver with new features and improvements,
> including:
> >> +
> >> +  * Added support for hot firmware upgrade.
> >> +  * Added support for error recovery.
> >> +  * Added support for querying and using COS classification in
> hardware.
> >> +  * Added LRO support Thor devices.
> >> +  * Update HWRM API to version 1.10.1.6
> >> +
> >
> > Hi Ajit,
> >
> > For next time, it is better to do the release notes / doc update in the
> patch
> > that adds the feature, that helps documenting features better.
> >
>
> Indeed, similar to .ini file change request, can you please add commits ids
> adding these features to the commit log as back reference? I am dropping
> this
> patch while merging for now.
>
Will do. Thanks

  reply	other threads:[~2019-11-20 16:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19 18:56 [dpdk-dev] [PATCH 0/3] bnxt patches Ajit Khaparde
2019-11-19 18:56 ` [dpdk-dev] [PATCH 1/3] net/bnxt: fix to ignore resource qcaps error with older FW Ajit Khaparde
2019-11-19 18:56 ` [dpdk-dev] [PATCH 2/3] net/bnxt: fix jumbo frame configuration in firmware Ajit Khaparde
2019-11-19 18:56 ` [dpdk-dev] [PATCH 3/3] doc: update release notes for Broadcom PMD Ajit Khaparde
2019-11-20  9:34   ` Ferruh Yigit
2019-11-20  9:45     ` Ferruh Yigit
2019-11-20 16:55       ` Ajit Khaparde [this message]
2019-11-21 23:34       ` [dpdk-dev] [PATCH v2 1/3] doc: update bnxt feature list Ajit Khaparde
2019-11-21 23:34         ` [dpdk-dev] [PATCH v2 2/3] doc: update release notes for Broadcom PMD Ajit Khaparde
2019-11-21 23:34         ` [dpdk-dev] [PATCH v2 3/3] net/bnxt: fix to free all the vnics during port stop Ajit Khaparde
2019-11-21 23:44           ` Ajit Khaparde
2019-11-19 19:01 ` [dpdk-dev] [PATCH 0/3] bnxt patches Ajit Khaparde

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=CACZ4nhs0DbdNPNpz0q3hct_f3_-NJ9cJhR6HjV83w37P1B6x+g@mail.gmail.com \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.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).