From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Kobylinski, MichalX" <michalx.kobylinski@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2 1/2] lpm: extend ip4 next_hop and add config structure
Date: Wed, 02 Mar 2016 17:35:20 +0100 [thread overview]
Message-ID: <2011283.cuAp1JmmEa@xps13> (raw)
In-Reply-To: <987EE72691933347B9F0B5C19E71B5BB1F04159F@IRSMSX101.ger.corp.intel.com>
2016-03-02 16:23, Kobylinski, MichalX:
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > Sent: Wednesday, March 2, 2016 4:29 PM
> > Is it possible to split the changes in next_hop and config structure?
>
> It is possible. Do you mean to put config structure into seperate patch-set?
If it makes sense, yes.
I don't know how strongly the changes are tied.
If possible, it's better to have progressive changes to make the patches
easier to understand.
next prev parent reply other threads:[~2016-03-02 16:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 12:12 [PATCH v2 0/2] Increase number of next hops for LPM IPv4 Michal Kobylinski
2016-01-29 12:12 ` [PATCH v2 1/2] lpm: extend ip4 next_hop and add config structure Michal Kobylinski
2016-02-18 10:02 ` Hunt, David
2016-03-02 15:28 ` Thomas Monjalon
2016-03-02 16:23 ` Kobylinski, MichalX
2016-03-02 16:35 ` Thomas Monjalon [this message]
2016-01-29 12:12 ` [PATCH 2/2] examples: update to use new lpm lib for ip4 Michal Kobylinski
2016-02-18 10:02 ` Hunt, David
2016-02-26 7:35 ` [PATCH v2 0/2] Increase number of next hops for LPM IPv4 Xu, HuilongX
2016-03-08 15:13 ` Thomas Monjalon
2016-03-08 15:53 ` Kobylinski, MichalX
2016-03-08 16:31 ` Thomas Monjalon
2016-03-08 21:00 ` Kobylinski, MichalX
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=2011283.cuAp1JmmEa@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=michalx.kobylinski@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.