From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Baruch Siach <baruch@tkos.co.il>
Cc: dev@dpdk.org, "Mcnamara, John" <john.mcnamara@intel.com>,
Olivier Matz <olivier.matz@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: correct description of attach to indirect mbuf
Date: Tue, 06 Dec 2016 18:08:42 +0100 [thread overview]
Message-ID: <1815752.S474otfYhx@xps13> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE20266F49B@IRSMSX103.ger.corp.intel.com>
> > > Thanks, please keep the doc fixes coming.
> > >
> > > It would be better to quote the function in fixed width text like:
> > > ``rte_pktmbuf_attach()``.
> >
> > None of the function names mentioned in this chapter are quoted. I can
> > post a fix for that, but I think it should be a separate patch.
> >
>
> Unfortunately, the documentation isn't very consistent in this. You can
> ignore it for this patch.
>
> Acked-by: John McNamara <john.mcnamara@intel.com>
Applied, thanks
prev parent reply other threads:[~2016-12-06 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 8:25 Baruch Siach
2016-12-06 11:03 ` Mcnamara, John
2016-12-06 11:11 ` Baruch Siach
2016-12-06 11:35 ` Mcnamara, John
2016-12-06 17:08 ` Thomas Monjalon [this message]
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=1815752.S474otfYhx@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=baruch@tkos.co.il \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=olivier.matz@6wind.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).