From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH v2 1/2] doc: add guide for debug and
	troubleshoot
Date: Mon, 26 Nov 2018 08:38:47 +0100
Message-ID: <15131024.QE2Qa9ZnEz@xps>
References: <20181107093553.28868-1-vipin.varghese@intel.com>
 <32834229.FtvUSCm64C@xps>
 <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D2C1F6E@BGSMSX101.gar.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Mcnamara, John" <john.mcnamara@intel.com>,
 "Kovacevic, Marko" <marko.kovacevic@intel.com>, "Byrne,
 Stephen1" <stephen1.byrne@intel.com>,
 "amol.patel.com@dpdk.org" <amol.patel.com@dpdk.org>,
 "honnappa.nagarahalli@arm.com" <honnappa.nagarahalli@arm.com>, "Dumitrescu,
 Cristian" <cristian.dumitrescu@intel.com>, "Burakov,
 Anatoly" <anatoly.burakov@intel.com>, "Richardson,
 Bruce" <bruce.richardson@intel.com>,
 "olivier.matz@6wind.com" <olivier.matz@6wind.com>
To: "Varghese, Vipin" <vipin.varghese@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com
 [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 860EE1B6E3
 for <dev@dpdk.org>; Mon, 26 Nov 2018 08:38:54 +0100 (CET)
In-Reply-To: <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D2C1F6E@BGSMSX101.gar.corp.intel.com>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

26/11/2018 04:53, Varghese, Vipin:
> Hi Thomas,
> 
> snipped
> 
> > >
> > > Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>
> > > Acked-by: Marko Kovacevic <marko.kovacevic@intel.com>
> > 
> > I was in the hope of seeing more reviews for this guide.
> 
> Thanks for the update will wait for feedbacks
> 
> > I have the feeling it is not ready for prime time.
> 
> ok
> 
> > We should take time to discuss what we want to see in such doc, and how
> > accurate it is.
> 
> Can you suggest a method in which stake holders can check the accuracy  as suggested?

I've already added more Cc's.
The other method is to contact people directly by email, IRC or ask during meeting.

> > PS: patch 1 depends on figures in patch 2, which is wrong.
> 
> I will spin v3 alternating the order

I think it can wait for more inputs.