From: Jerin Jacob <jerinjacobk@gmail.com>
To: "Yan, Zhirun" <zhirun.yan@intel.com>
Cc: "jerinj@marvell.com" <jerinj@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Kiran Kumar K <kirankumark@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"pbhagavatula@marvell.com" <pbhagavatula@marvell.com>
Subject: Re: [dpdk-dev] [PATCH v1] doc: add inbuilt graph nodes data flow
Date: Thu, 20 Jul 2023 12:04:18 +0530 [thread overview]
Message-ID: <CALBAE1OyNz=rven-vthmnQe-t0=dKn6qxCCLBcXh=PBENXBOng@mail.gmail.com> (raw)
In-Reply-To: <SN7PR11MB67753A73894AF41BF5D5097D8526A@SN7PR11MB6775.namprd11.prod.outlook.com>
On Mon, Jun 26, 2023 at 11:34 AM Yan, Zhirun <zhirun.yan@intel.com> wrote:
>
>
>
> > -----Original Message-----
> > From: jerinj@marvell.com <jerinj@marvell.com>
> > Sent: Friday, June 23, 2023 3:36 PM
> > To: dev@dpdk.org; Jerin Jacob <jerinj@marvell.com>; Kiran Kumar K
> > <kirankumark@marvell.com>; Nithin Dabilpuram <ndabilpuram@marvell.com>;
> > Yan, Zhirun <zhirun.yan@intel.com>
> > Cc: thomas@monjalon.net; pbhagavatula@marvell.com
> > Subject: [dpdk-dev] [PATCH v1] doc: add inbuilt graph nodes data flow
> >
> > From: Jerin Jacob <jerinj@marvell.com>
> >
> > Added diagram to depict the data flow between inbuilt graph nodes.
> >
> > In order to avoid graphviz package dependency to DPDK documentation, manual
> > step added to create a svg file from the dot file. The details for the same is
> > documented in graph_inbuilt_node_flow.svg as a comment.
> >
> > Signed-off-by: Jerin Jacob <jerinj@marvell.com>
> > ---
>
> Reviewed-by: Zhirun Yan <zhirun.yan@intel.com>
Ping for merge
next prev parent reply other threads:[~2023-07-20 6:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 7:36 jerinj
2023-06-26 6:04 ` Yan, Zhirun
2023-07-20 6:34 ` Jerin Jacob [this message]
2023-07-25 8:35 ` 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='CALBAE1OyNz=rven-vthmnQe-t0=dKn6qxCCLBcXh=PBENXBOng@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=thomas@monjalon.net \
--cc=zhirun.yan@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).