From: David Miller <davem@davemloft.net>
To: igal.liberman@freescale.com
Cc: netdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, scottwood@freescale.com,
madalin.bucur@freescale.com, pebolle@tiscali.nl,
joakim.tjernlund@transmode.se, ppc@mindchasers.com,
stephen@networkplumber.org
Subject: Re: [v4, 0/9] Freescale DPAA FMan
Date: Fri, 07 Aug 2015 15:31:02 -0700 (PDT) [thread overview]
Message-ID: <20150807.153102.533553009548852567.davem@davemloft.net> (raw)
In-Reply-To: <1438766725-8053-1-git-send-email-igal.liberman@freescale.com>
From: <igal.liberman@freescale.com>
Date: Wed, 5 Aug 2015 12:25:16 +0300
> The Freescale Data Path Acceleration Architecture (DPAA)
> is a set of hardware components on specific QorIQ multicore processors.
> This architecture provides the infrastructure to support simplified
> sharing of networking interfaces and accelerators by multiple CPU cores
> and the accelerators.
I think the directory and code structure of this new driver is
quite excessive.
Because you've split things up _so_ much, you have to have
all of these directories, and even worse and much more important
to me you have to export so many functions from one source file
to another.
I think this is way too much.
For example, in one file you have a bunch of initialization routines.
init_a(), init_b(), init_c(), and you export them all. Then they
are always called in sequence:
init_a();
init_b();
init_c();
This is completely pointless. You just needed to export one
function which calls all three functions.
The namespace pollution of this driver is out of control.
You really need to completely rework the architecture and
layout of this driver before I will even begin to review it
again.
And the lack of review interest by other developers should be an
indication to you how undesirable this code submission is to read.
Thanks.
next prev parent reply other threads:[~2015-08-07 22:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 9:25 [v4, 0/9] Freescale DPAA FMan igal.liberman
2015-08-05 9:25 ` [v4, 1/9] fsl/fman: Add the FMan FLIB igal.liberman
2015-08-05 9:25 ` [v4, 2/9] fsl/fman: Add the FMan port FLIB igal.liberman
2015-08-05 9:25 ` [v4, 3/9] fsl/fman: Add the FMan MAC FLIB igal.liberman
2015-08-05 9:25 ` [v4, 4/9] fsl/fman: Add FMan MURAM support igal.liberman
2015-08-05 9:25 ` [v4, 5/9] fsl/fman: Add Frame Manager support igal.liberman
2015-08-05 9:25 ` [v4, 6/9] fsl/fman: Add FMan MAC support igal.liberman
2015-08-05 9:25 ` [v4, 7/9] fsl/fman: Add FMan SP support igal.liberman
2015-08-05 9:25 ` [v4, 8/9] fsl/fman: Add FMan Port Support igal.liberman
2015-08-05 9:25 ` [v4, 9/9] fsl/fman: Add FMan MAC driver igal.liberman
2015-08-07 22:31 ` David Miller [this message]
2015-08-10 19:55 ` [v4, 0/9] Freescale DPAA FMan Liberman Igal
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=20150807.153102.533553009548852567.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=igal.liberman@freescale.com \
--cc=joakim.tjernlund@transmode.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madalin.bucur@freescale.com \
--cc=netdev@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=ppc@mindchasers.com \
--cc=scottwood@freescale.com \
--cc=stephen@networkplumber.org \
/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).