> -----Original Message-----
> From: Thomas Monjalon <[email protected]>
> Sent: Monday, November 26, 2018 1:09 PM
> To: Varghese, Vipin <[email protected]>
> Cc: [email protected]; Mcnamara, John <[email protected]>; Kovacevic,
> Marko <[email protected]>; Byrne, Stephen1
> <[email protected]>; [email protected];
> [email protected]; Dumitrescu, Cristian
> <[email protected]>; Burakov, Anatoly
> <[email protected]>; Richardson, Bruce
> <[email protected]>; [email protected]
> Subject: Re: [dpdk-dev] [PATCH v2 1/2] doc: add guide for debug and
> troubleshoot
>
> 26/11/2018 04:53, Varghese, Vipin:
> > Hi Thomas,
> >
> > snipped
> >
> > > >
> > > > Signed-off-by: Vipin Varghese <[email protected]>
> > > > Acked-by: Marko Kovacevic <[email protected]>
> > >
> > > 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.
>
>
Ok sure
