[dpdk-dev] [v4 0/3] Merge l3fwd-acl and l3fwd
rkerur at gmail.com
Wed Mar 8 22:50:47 CET 2017
Kindly let me know new 'v5' patch follows dpdk guidelines?
I just followed what's in the dpdk contributing code guidelines.
- git format-patch -3 -o patch/ -v 5 --cover-letter
- git send-email --to dev at dpdk.org --in-reply-to <v4-MSGID> patch/*
On Mon, Mar 6, 2017 at 3:20 PM, Ravi Kerur <rkerur at gmail.com> wrote:
> Hi John,
> Should I work with documentation team to update the document? If yes,
> please let me know the contact information.
> On Mon, Mar 6, 2017 at 5:33 AM, Mcnamara, John <john.mcnamara at intel.com>
>> > -----Original Message-----
>> > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Ravi Kerur
>> > Sent: Sunday, March 5, 2017 7:47 PM
>> > To: dev at dpdk.org
>> > Cc: Ananyev, Konstantin <konstantin.ananyev at intel.com>; Richardson,
>> > <bruce.richardson at intel.com>; Ravi Kerur <rkerur at gmail.com>
>> > Subject: [dpdk-dev] [v4 0/3] Merge l3fwd-acl and l3fwd
>> > This patchset merges l3fwd-acl and l3fwd code into common directory.
>> > Adds file read options to build LPM and EM tables.
>> Hi Ravi,
>> Thanks to this. It seems like a good change. There are probably too many
>> L2/L3 variants and some of them should be merged.
>> Note, you will also have to merge the sample app guides in some sensible
More information about the dev