[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <AM5PR0402MB26915EFC135F6ECEBA92C89DEC850@AM5PR0402MB2691.eurprd04.prod.outlook.com>
Date: Wed, 23 Aug 2017 05:16:52 +0000
From: Madalin-cristian Bucur <madalin.bucur@....com>
To: David Miller <davem@...emloft.net>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Florinel Iordache" <florinel.iordache@....com>
Subject: RE: [PATCH v2 1/6] fsl/fman: enable FMan Keygen
> -----Original Message-----
> From: David Miller [mailto:davem@...emloft.net]
> Sent: Wednesday, August 23, 2017 7:47 AM
> To: Madalin-cristian Bucur <madalin.bucur@....com>
> Cc: netdev@...r.kernel.org; linuxppc-dev@...ts.ozlabs.org; linux-
> kernel@...r.kernel.org
> Subject: Re: [PATCH v2 1/6] fsl/fman: enable FMan Keygen
>
> From: Madalin-cristian Bucur <madalin.bucur@....com>
> Date: Wed, 23 Aug 2017 04:36:56 +0000
>
> > The struct fman is only visible in the fman file, the fman port
> > module uses struct fman as an opaque pointer, thus this export.
>
> Don't use that programming model.
>
> Export the datastructure properly to it's users.
>
> This abstraction scheme is so wasteful and costly.
Normally does not come with this cost, it's this case where one of the
sub-modules needs to call into another that gets things complicated.
I'll move struct fman to the header file.
Thanks,
Madalin
Powered by blists - more mailing lists