> > > 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
> -Original Message-
> From: Baruch Siach [mailto:bar...@tkos.co.il]
> Sent: Tuesday, December 6, 2016 11:11 AM
> To: Mcnamara, John
> Cc: dev@dpdk.org; Olivier Matz
> Subject: Re: [PATCH v2] doc: correct description of attach to indirect
> mbuf
>
> ...
> > Thanks, please keep the doc fi
Hi John,
On Tue, Dec 06, 2016 at 11:03:18AM +, Mcnamara, John wrote:
> > -Original Message-
> > From: Baruch Siach [mailto:bar...@tkos.co.il]
> > Sent: Tuesday, December 6, 2016 8:25 AM
> > To: dev@dpdk.org
> > Cc: Mcnamara, John ; Olivier Matz
> > ; Baruch Siach
> > Subject: [PATCH v
> -Original Message-
> From: Baruch Siach [mailto:bar...@tkos.co.il]
> Sent: Tuesday, December 6, 2016 8:25 AM
> To: dev@dpdk.org
> Cc: Mcnamara, John ; Olivier Matz
> ; Baruch Siach
> Subject: [PATCH v2] doc: correct description of attach to indirect mbuf
>
> Since commit 4a96e8b652181
Since commit 4a96e8b652181 ("mbuf: allow to clone an indirect mbuf")
attaching to an indirect mbuf creates a clone of that mbuf. Update the mbuf
documentation to match.
Signed-off-by: Baruch Siach
---
v2: fix checkpatch issues: long commit log lines, short commit id
---
doc/guides/prog_guide/mbu
5 matches
Mail list logo
