[dpdk-dev] [PATCH v3 1/8] raw/ioat: add initial support for ioat rawdev driver

Bruce Richardson bruce.richardson at intel.com
Fri Jun 28 14:43:46 CEST 2019


On Thu, Jun 27, 2019 at 12:55:12PM +0100, Burakov, Anatoly wrote:
> On 27-Jun-19 11:40 AM, Bruce Richardson wrote:
> > Add stubs for ioat rawdev driver support in DPDK, specifically:
> > 
> >    * makefile and meson build hooks
> >    * initial public header file
> >    * rawdev main C file, with probe and release functions
> >    * release note update announcing the driver
> >    * initial documentation for the new section in the rawdev doc
> >    * unit test stubs for device unit tests
> > 
> > Signed-off-by: Bruce Richardson <bruce.richardson at intel.com>
> > 
> > ---
> 
> <snip>
> 
> >   NXP DPAA2 QDMA
> >   M: Nipun Gupta <nipun.gupta at nxp.com>
> >   F: drivers/raw/dpaa2_qdma/
> > @@ -1078,7 +1083,6 @@ M: Nipun Gupta <nipun.gupta at nxp.com>
> >   F: drivers/raw/dpaa2_cmdif/
> >   F: doc/guides/rawdevs/dpaa2_cmdif.rst
> > -
> >   Packet processing
> 
> Unnecessary whitespace change :)
> 

Thanks, good catch. 

> >   -----------------
> > diff --git a/app/test/test_rawdev.c b/app/test/test_rawdev.c
> > index 043a38a13..88549fb61 100644
> > --- a/app/test/test_rawdev.c
> > +++ b/app/test/test_rawdev.c
> > @@ -25,3 +25,11 @@ test_rawdev_selftest_skeleton(void)
> >   }
> 
> <snip>
> 
> > diff --git a/doc/guides/rel_notes/release_19_08.rst b/doc/guides/rel_notes/release_19_08.rst
> > index 3da266705..720c13f8b 100644
> > --- a/doc/guides/rel_notes/release_19_08.rst
> > +++ b/doc/guides/rel_notes/release_19_08.rst
> > @@ -1,6 +1,8 @@
> >   ..  SPDX-License-Identifier: BSD-3-Clause
> >       Copyright 2019 The DPDK contributors
> > +.. include:: <isonum.txt>
> > +
> 
> Is this accidental? This doesn't look related to this patch.
> 
No, it's not accidental. It's the sphinx / rst include which allows the use
of the actual symbols for (c) (R) etc. I make use of those symbols in the
official product names in the following documentation. [It's a useful
include that I think should always be put in our docs.]


More information about the dev mailing list