From: Thomas Monjalon <thomas@monjalon.net>
To: "Varghese, Vipin" <vipin.varghese@intel.com>
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>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] doc: add guide for debug and troubleshoot
Date: Mon, 26 Nov 2018 08:38:47 +0100 [thread overview]
Message-ID: <15131024.QE2Qa9ZnEz@xps> (raw)
In-Reply-To: <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D2C1F6E@BGSMSX101.gar.corp.intel.com>
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.
next prev parent reply other threads:[~2018-11-26 7:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 9:35 [dpdk-dev] [PATCH " Vipin Varghese
2018-11-07 9:35 ` [dpdk-dev] [PATCH 2/2] doc: add svg for debug and troubleshoot guide Vipin Varghese
2018-11-08 14:46 ` Kovacevic, Marko
2018-11-08 14:43 ` [dpdk-dev] [PATCH 1/2] doc: add guide for debug and troubleshoot Kovacevic, Marko
2018-11-09 10:06 ` [dpdk-dev] [PATCH v2 " Vipin Varghese
2018-11-09 10:06 ` [dpdk-dev] [PATCH v2 2/2] doc: add svg for debug and troubleshoot guide Vipin Varghese
2018-11-09 15:03 ` [dpdk-dev] [PATCH v2 1/2] doc: add guide for debug and troubleshoot Vipin Varghese
2018-11-09 15:03 ` [dpdk-dev] [PATCH v2 2/2] doc: add svg for debug and troubleshoot guide Vipin Varghese
2018-11-25 10:21 ` [dpdk-dev] [PATCH v2 1/2] doc: add guide for debug and troubleshoot Thomas Monjalon
2018-11-26 3:53 ` Varghese, Vipin
2018-11-26 7:38 ` Thomas Monjalon [this message]
2018-11-26 8:22 ` Varghese, Vipin
2018-12-28 5:30 ` Varghese, Vipin
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=15131024.QE2Qa9ZnEz@xps \
--to=thomas@monjalon.net \
--cc=amol.patel.com@dpdk.org \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=olivier.matz@6wind.com \
--cc=stephen1.byrne@intel.com \
--cc=vipin.varghese@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).