From: Jerin Jacob <jerinjacobk@gmail.com>
To: Ashwin Sekhar T K <asekhar@marvell.com>
Cc: dev@dpdk.org, Jerin Jacob <jerinj@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
skori@marvell.com, skoteshwar@marvell.com,
pbhagavatula@marvell.com, psatheesh@marvell.com,
anoobj@marvell.com, gakhil@marvell.com, hkalra@marvell.com
Subject: Re: [PATCH] doc: fix typo in graph lib doc
Date: Thu, 4 May 2023 10:19:58 +0530 [thread overview]
Message-ID: <CALBAE1MubejAscx-G4GZSd0C0Fk4X_8ieh3nOrQW94EFQ7G0rg@mail.gmail.com> (raw)
In-Reply-To: <20230504043135.3977224-1-asekhar@marvell.com>
On Thu, May 4, 2023 at 10:01 AM Ashwin Sekhar T K <asekhar@marvell.com> wrote:
>
> Fix typo in graph lib doc.
>
> Fixes: 4dc6d8e63c168 ("doc: add graph library guide")
>
> Signed-off-by: Ashwin Sekhar T K <asekhar@marvell.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
> ---
> doc/guides/prog_guide/graph_lib.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/guides/prog_guide/graph_lib.rst b/doc/guides/prog_guide/graph_lib.rst
> index 1cfdc86433..4ab0623f44 100644
> --- a/doc/guides/prog_guide/graph_lib.rst
> +++ b/doc/guides/prog_guide/graph_lib.rst
> @@ -173,7 +173,7 @@ Create the graph object
> ~~~~~~~~~~~~~~~~~~~~~~~
> Now that the nodes are linked, Its time to create a graph by including
> the required nodes. The application can provide a set of node patterns to
> -form a graph object. The ``famish()`` API used underneath for the pattern
> +form a graph object. The ``fnmatch()`` API used underneath for the pattern
> matching to include the required nodes. After the graph create any changes to
> nodes or graph is not allowed.
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2023-05-04 4:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 4:31 Ashwin Sekhar T K
2023-05-04 4:49 ` Jerin Jacob [this message]
2023-06-12 17:10 ` 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=CALBAE1MubejAscx-G4GZSd0C0Fk4X_8ieh3nOrQW94EFQ7G0rg@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=anoobj@marvell.com \
--cc=asekhar@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=hkalra@marvell.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=psatheesh@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.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).