From: Ray Kinsella <mdr@ashroe.eu>
To: Ye Xiaolong <xiaolong.ye@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
"Kovacevic, Marko" <marko.kovacevic@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [dpdk-dev] [PATCH v6] doc: introduce openwrt how-to guide
Date: Tue, 18 Feb 2020 10:08:56 +0000 [thread overview]
Message-ID: <616a37b6-1d94-ee83-122e-fdfdf8c625e0@ashroe.eu> (raw)
In-Reply-To: <20200218094937.GC104429@intel.com>
On 18/02/2020 09:49, Ye Xiaolong wrote:
> On 02/18, Thomas Monjalon wrote:
>> 18/02/2020 10:12, Ray Kinsella:
>>> On 18/02/2020 08:26, Mcnamara, John wrote:
>>>> From: Ray Kinsella <mdr@ashroe.eu>
>>>>> So to be clear.
>>>>> I see that documentation like this is brittle and has a limited lifespan.
>>>>> I can almost guarantee the next version of DPDK or OpenWRT will break it.
>>>>> (and how would we know?)
>>>>>
>>>>> Much better to do this in the right place - OpenWRT.
>>>>
>>>> Hi Ray,
>>>>
>>>> These comments are a little late, we have been through 6 revisions.
>>>
>>> Understood.
>>>
>>>> I suggest putting the doc in as it is, since it useful, and revise it to make it more update proof in the next release.
>>>
>>> Agreed - feedback was late.
>>> I am registering my protest, that this cannot be called 'done' - further work is required to make this sustainable.
>>
>> I agree the most important is to work on DPDK integration.
>> Would be nice to have DPDK integrated as a package in OpenWrt
>> and in Buildroot as well.
>
> Yes, agree this would be a better and clean solution.
>
>> And please make sure meson allows to choose any toolchain easily.
>
> It's in my todo list now. :)
>
> Thanks,
> Xiaolong
>>
>> Thanks
>>
>>
perfect, thank you.
next prev parent reply other threads:[~2020-02-18 10:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 8:19 [dpdk-dev] [PATCH] doc: introduce openwrt how-to guide Xiaolong Ye
2019-11-29 10:09 ` Bruce Richardson
2019-11-29 15:03 ` Ye Xiaolong
2019-11-29 16:59 ` Stephen Hemminger
2019-12-01 11:30 ` Ye Xiaolong
2019-12-02 6:34 ` [dpdk-dev] [PATCH v2] " Xiaolong Ye
2019-12-02 7:31 ` Jerin Jacob
2019-12-02 8:09 ` Ye Xiaolong
2019-12-12 2:25 ` [dpdk-dev] [PATCH v3] " Xiaolong Ye
2019-12-16 3:01 ` [dpdk-dev] [PATCH v4] " Xiaolong Ye
2019-12-19 6:05 ` Zhang, Xiao
2020-01-17 13:46 ` Mcnamara, John
2020-01-18 1:52 ` Ye Xiaolong
2020-01-18 5:48 ` [dpdk-dev] [PATCH v5] " Xiaolong Ye
2020-01-22 12:34 ` Mcnamara, John
2020-02-16 11:04 ` Thomas Monjalon
2020-02-16 17:29 ` Ye Xiaolong
2020-02-16 18:02 ` Thomas Monjalon
2020-02-17 1:18 ` Ye Xiaolong
2020-02-17 3:12 ` Dmitry Kozlyuk
2020-02-17 6:21 ` Ye Xiaolong
2020-02-17 2:47 ` [dpdk-dev] [PATCH v6] " Xiaolong Ye
2020-02-17 15:08 ` Ray Kinsella
2020-02-17 15:44 ` Ye Xiaolong
2020-02-17 15:49 ` Ray Kinsella
2020-02-18 8:26 ` Mcnamara, John
2020-02-18 9:12 ` Ray Kinsella
2020-02-18 9:32 ` Thomas Monjalon
2020-02-18 9:49 ` Ye Xiaolong
2020-02-18 10:08 ` Ray Kinsella [this message]
2020-02-21 21:08 ` 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=616a37b6-1d94-ee83-122e-fdfdf8c625e0@ashroe.eu \
--to=mdr@ashroe.eu \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--cc=xiaolong.ye@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.