From: Vladyslav Buslov <Vladyslav.Buslov@harmonicinc.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] lpm: extend IPv6 next hop field
Date: Wed, 22 Feb 2017 12:33:59 +0000 [thread overview]
Message-ID: <MWHPR11MB1360C9836F21FE9C1405FB9C9D500@MWHPR11MB1360.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20170222120258.GA12656@bricha3-MOBL3.ger.corp.intel.com>
Hi Bruce,
Yes, v2 patch is same as v1 + indentation changes according to checkpatch warnings.
Regards,
Vlad
> -----Original Message-----
> From: Bruce Richardson [mailto:bruce.richardson@intel.com]
> Sent: Wednesday, February 22, 2017 2:03 PM
> To: Vladyslav Buslov
> Cc: dev@dpdk.org
> Subject: Re: [PATCH v2] lpm: extend IPv6 next hop field
>
> On Tue, Feb 21, 2017 at 04:46:39PM +0200, Vladyslav Buslov wrote:
> > This patch extend next_hop field from 8-bits to 21-bits in LPM library
> > for IPv6.
> >
> > Added versioning symbols to functions and updated library and
> > applications that have a dependency on LPM library.
> >
> > Signed-off-by: Vladyslav Buslov <vladyslav.buslov@harmonicinc.com>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
>
> Hi Vlad,
>
> Thanks for the V2.
> I assume that this is just the V1 with the checkpatch issues fixed, right? For
> future use, please include just below the cut line "---" a short list of what has
> changed since the previous version, so that we know what to look for if we
> already have reviewed the previous version.
> For minor changes in code, like in this case, you can also keep the ack on the
> resubmission, putting it just below the signoff like above.
>
> /Bruce
next prev parent reply other threads:[~2017-02-22 12:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 17:14 [dpdk-dev] [PATCH] " Vladyslav Buslov
2017-02-21 11:23 ` Bruce Richardson
2017-02-21 11:37 ` Vladyslav Buslov
2017-02-21 12:07 ` Bruce Richardson
2017-02-21 14:46 ` [dpdk-dev] [PATCH v2] " Vladyslav Buslov
2017-02-22 12:02 ` Bruce Richardson
2017-02-22 12:33 ` Vladyslav Buslov [this message]
2017-03-09 15:37 ` Thomas Monjalon
2017-03-14 17:17 ` [dpdk-dev] [PATCH v3] " Vladyslav Buslov
2017-03-15 17:50 ` 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=MWHPR11MB1360C9836F21FE9C1405FB9C9D500@MWHPR11MB1360.namprd11.prod.outlook.com \
--to=vladyslav.buslov@harmonicinc.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.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).