DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
	dev@dpdk.org, dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: update release notes
Date: Wed, 22 Apr 2020 23:42:18 +0200	[thread overview]
Message-ID: <3719125.2iPT33SAM4@thomas> (raw)
In-Reply-To: <CACZ4nhuUog4LL+t_djU=OvGGNEtXTpAa50JrpnB7_nCAS6KQBg@mail.gmail.com>

18/04/2020 00:40, Ajit Khaparde:
> On Fri, Apr 17, 2020 at 3:29 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> > On 4/17/2020 5:35 PM, Ajit Khaparde wrote:
> > > Update release notes for 20.05 release with Broadcom PMD improvements:
> > >
> > The release notes should updated with the patchset that adds the feature,
> > instead of as a separate patch, can you please pay attention for next sets.
> >
> > Also please add the notes in the order that has been described in the
> > comment of
> > the section.
> >
> > Applied to dpdk-next-net/master, thanks.
> >
> Will do. Thanks Ferruh.

I will squash in the appropriate patches,
so we can git blame release notes
to find the code change.
Thanks for double checking release notes for the next features.



  reply	other threads:[~2020-04-22 21:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-17 16:35 Ajit Khaparde
2020-04-17 22:29 ` Ferruh Yigit
2020-04-17 22:40   ` Ajit Khaparde
2020-04-22 21:42     ` Thomas Monjalon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-05-10  4:19 Qi Zhang
2016-07-01 14:10 Bernard Iremonger
2016-07-14 13:32 ` Thomas Monjalon
2016-07-14 13:45   ` Iremonger, Bernard
2016-07-14 15:04     ` Thomas Monjalon
2016-07-14 15:34       ` Iremonger, Bernard
2016-07-22 17:14 ` Thomas Monjalon
2015-11-12  3:18 Helin Zhang
2015-12-13 23:26 ` Thomas Monjalon

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=3719125.2iPT33SAM4@thomas \
    --to=thomas@monjalon.net \
    --cc=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).