John, Konstantin, 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 [email protected] --in-reply-to <v4-MSGID> patch/* Thanks. On Mon, Mar 6, 2017 at 3:20 PM, Ravi Kerur <[email protected]> wrote: > Hi John, > > Should I work with documentation team to update the document? If yes, > please let me know the contact information. > > Thanks. > > On Mon, Mar 6, 2017 at 5:33 AM, Mcnamara, John <[email protected]> > wrote: > >> > -----Original Message----- >> > From: dev [mailto:[email protected]] On Behalf Of Ravi Kerur >> > Sent: Sunday, March 5, 2017 7:47 PM >> > To: [email protected] >> > Cc: Ananyev, Konstantin <[email protected]>; Richardson, >> Bruce >> > <[email protected]>; Ravi Kerur <[email protected]> >> > 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 >> way: >> >> http://dpdk.org/doc/guides/sample_app_ug/l3_forward.html >> http://dpdk.org/doc/guides/sample_app_ug/l3_forward_access_ctrl.html >> >> John >> >> >
