DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: "Pattan, Reshma" <reshma.pattan@intel.com>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/2] pdump: cleanups
Date: Tue, 12 Nov 2019 21:37:32 +0100	[thread overview]
Message-ID: <CAJFAV8xN5qS__5JspquYf8oHmFVGAWPw2=xiTsP=Uu3qMDHgmQ@mail.gmail.com> (raw)
In-Reply-To: <20191108164717.7708-1-stephen@networkplumber.org>

On Fri, Nov 8, 2019 at 5:47 PM Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> These are a couple of small cleanups for 19.10 which

Stephen, we might be a bit late for this release, but it is still 19.11 :-)

> came out of work on pcapng support. Full pcapng support
> and BPF are planned for DPDK 20.02.
>
> Stephen Hemminger (2):
>   pdump: use new pktmbuf copy function
>   pdump: use dynamic logtype
>
>  lib/librte_pdump/rte_pdump.c | 139 ++++++++++-------------------------
>  1 file changed, 40 insertions(+), 99 deletions(-)
>
> v2 - replace new log message from info_get as well

Overall looks good.
Reshma, review please.


Thanks.

-- 
David Marchand


  parent reply	other threads:[~2019-11-12 20:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08  4:38 [dpdk-dev] [PATCH " Stephen Hemminger
2019-11-08  4:38 ` [dpdk-dev] [PATCH 1/2] pdump: use new pktmbuf copy function Stephen Hemminger
2019-11-08  4:38 ` [dpdk-dev] [PATCH 2/2] pdump: use dynamic logtype Stephen Hemminger
2019-11-08  8:13   ` David Marchand
2019-11-08 16:19     ` Stephen Hemminger
2019-11-08 16:47 ` [dpdk-dev] [PATCH v2 0/2] pdump: cleanups Stephen Hemminger
2019-11-08 16:47   ` [dpdk-dev] [PATCH v2 1/2] pdump: use new pktmbuf copy function Stephen Hemminger
2019-11-08 16:47   ` [dpdk-dev] [PATCH v2 2/2] pdump: use dynamic logtype Stephen Hemminger
2019-11-12 20:37   ` David Marchand [this message]
2019-11-15 12:50   ` [dpdk-dev] [PATCH v2 0/2] pdump: cleanups Pattan, Reshma
2020-02-05 20:20     ` David Marchand
2020-06-11  8:46   ` Dong Zhou

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='CAJFAV8xN5qS__5JspquYf8oHmFVGAWPw2=xiTsP=Uu3qMDHgmQ@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=reshma.pattan@intel.com \
    --cc=stephen@networkplumber.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).