From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Kobylinski, MichalX" <michalx.kobylinski@intel.com>,
bruce.richardson@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Question about patchset order.
Date: Tue, 23 Feb 2016 18:34:38 +0100 [thread overview]
Message-ID: <1565638.IGO4Cj2mt5@xps13> (raw)
In-Reply-To: <987EE72691933347B9F0B5C19E71B5BB1F02E312@IRSMSX101.ger.corp.intel.com>
2016-02-23 16:17, Kobylinski, MichalX:
> Hi Thomas,
> I sent in January a patch-set that extends to 24 bits a next_hop field in lpm library:
> http://dpdk.org/dev/patchwork/patch/10249/
> http://dpdk.org/dev/patchwork/patch/10250/
>
> also Jerin Jakob sent his patch-set with ARM architecture support in lpm library.
> http://dpdk.org/dev/patchwork/patch/10478/
> http://dpdk.org/dev/patchwork/patch/10479/
> http://dpdk.org/dev/patchwork/patch/10480/
>
> Could you write please, in which order do you prefer to apply these two patch-sets?
> This information will be helpful to predict the risk and estimate additional work.
Thanks for bringing up the LPM patches.
I would prefer to follow the advice of Bruce who has well followed
these interactions.
next prev parent reply other threads:[~2016-02-23 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 16:17 Kobylinski, MichalX
2016-02-23 17:34 ` Thomas Monjalon [this message]
2016-03-02 0:07 ` Bruce Richardson
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=1565638.IGO4Cj2mt5@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bruce.richardson@intel.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 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).