From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Varghese, Vipin" <vipin.varghese@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Kovacevic, Marko" <marko.kovacevic@intel.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Iremonger, Bernard" <bernard.iremonger@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: "Padubidri, Sanjay A" <sanjay.padubidri@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc/testpmd: update compile steps for bpf examples
Date: Tue, 7 May 2019 15:07:13 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23F612089@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <20190507084112.35296-1-vipin.varghese@intel.com>
> -----Original Message-----
> From: Varghese, Vipin
> Sent: Tuesday, May 7, 2019 9:41 AM
> To: dev@dpdk.org; Kovacevic, Marko <marko.kovacevic@intel.com>; Mcnamara,
> John <john.mcnamara@intel.com>; Lu, Wenzhuo <wenzhuo.lu@intel.com>; Wu,
> Jingjing <jingjing.wu@intel.com>; Iremonger, Bernard
> <bernard.iremonger@intel.com>
> Cc: Padubidri, Sanjay A <sanjay.padubidri@intel.com>; Varghese, Vipin
> <vipin.varghese@intel.com>
> Subject: [PATCH] doc/testpmd: update compile steps for bpf examples
>
> Add the missing arguments for compiling t2.c and t3.c BPF examples.
>
Acked from a doc point of view. Maintainers should check if the instructions are okay.
Acked-by: John McNamara <john.mcnamara@intel.com>
next prev parent reply other threads:[~2019-05-07 15:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 8:41 Vipin Varghese
2019-05-07 8:41 ` Vipin Varghese
2019-05-07 15:07 ` Mcnamara, John [this message]
2019-05-07 15:07 ` Mcnamara, John
2019-05-09 22:31 ` Thomas Monjalon
2019-05-09 22:31 ` Thomas Monjalon
2019-05-10 1:41 ` Varghese, Vipin
2019-05-10 1:41 ` Varghese, Vipin
2019-05-23 13:47 ` [dpdk-dev] [PATCH v2] " Vipin Varghese
2019-05-29 11:17 ` Thomas Monjalon
2019-05-30 15:40 ` Varghese, Vipin
2019-06-10 5:41 ` [dpdk-dev] [PATCH v3] " Vipin Varghese
2023-06-12 16:31 ` Stephen Hemminger
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=B27915DBBA3421428155699D51E4CFE23F612089@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=sanjay.padubidri@intel.com \
--cc=vipin.varghese@intel.com \
--cc=wenzhuo.lu@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).