> -----Original Message----- > From: Joe Perches <[email protected]> > Sent: Thursday, June 25, 2020 8:32 PM > To: Kirsher, Jeffrey T <[email protected]>; [email protected] > Cc: Michael, Alice <[email protected]>; [email protected]; > [email protected]; [email protected]; Brady, Alan > <[email protected]>; Burra, Phani R <[email protected]>; Hay, > Joshua A <[email protected]>; Chittim, Madhu > <[email protected]>; Linga, Pavan Kumar > <[email protected]>; Skidmore, Donald C > <[email protected]>; Brandeburg, Jesse > <[email protected]>; Samudrala, Sridhar > <[email protected]> > Subject: Re: [net-next v3 14/15] iecm: Add iecm to the kernel build system > > On Thu, 2020-06-25 at 19:07 -0700, Jeff Kirsher wrote: > > From: Alice Michael <[email protected]> > [] > > diff --git a/Documentation/networking/device_drivers/intel/iecm.rst > > b/Documentation/networking/device_drivers/intel/iecm.rst > [] > > @@ -0,0 +1,93 @@ > > +.. SPDX-License-Identifier: GPL-2.0 > > + > > +======================== > > +Intel Ethernet Common Module > > +======================== > > + > > +The Intel Ethernet Common Module is meant to serve as an abstraction > > +layer between device specific implementation details and common net > > +device driver flows. This library provides several function hooks > > +which allow a device driver to specify register addresses, control > > +queue communications, and other device specific functionality. Some > > +functions are required to be implemented while others have a default > > +implementation that is used when none is supplied by the device > > +driver. Doing this, a device driver can be written to take advantage > > +of existing code while also giving the flexibility to implement device > > specific > features. > > + > > +The common use case for this library is for a network device driver > > +that wants > > to > > > +specify its own device specific details but also leverage the more > > +common code flows found in network device drivers. >
Will fix, thanks. Alan
