From: Alexander Graf <agraf@suse.de>
To: "J. German Rivera" <German.Rivera@freescale.com>,
gregkh@linuxfoundation.org, arnd@arndb.de,
linux-kernel@vger.kernel.org
Cc: stuart.yoder@freescale.com, Kim.Phillips@freescale.com,
scottwood@freescale.com, bhamciu1@freescale.com,
R89243@freescale.com, Geoff.Thorpe@freescale.com,
bhupesh.sharma@freescale.com, nir.erez@freescale.com,
richard.schmitt@freescale.com
Subject: Re: [PATCH v2 1/1] drivers/bus: fsl-mc object allocator driver
Date: Thu, 26 Feb 2015 15:25:26 +0100 [thread overview]
Message-ID: <54EF2CD6.2050608@suse.de> (raw)
In-Reply-To: <1424818219-16142-2-git-send-email-German.Rivera@freescale.com>
On 24.02.15 23:50, J. German Rivera wrote:
> The fsl-mc object allocator driver manages "allocatable" fsl-mc
> objects such as DPBPs, DPMCPs and DPCONs. It provides services to
I'd recommend to explain what these abbreviations mean. It's
ridiculously hard to remember what they are about. So please put their
full name at least into the patch description and into the headers of
their respective handling files.
Also, can we maybe split the patches into the minimal set required to
get one driver working? I hate to see lots of functions land in upstream
that are never called from anywhere. At the end of the day, I care about
vertical coverage, not horizontal. All of your patches so far are
horizontal.
So please pick one driver, choose the subset required to make bus
enumeration, DPRC handling and the few objects required for that one
driver work and then let's try to push it upstream.
Once that's done we can easily extend the interface incrementally with
every other new driver from that point on.
Alex
next prev parent reply other threads:[~2015-02-26 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 22:50 [PATCH v2 0/1] drivers/bus: fsl-mc object allocator driver J. German Rivera
2015-02-24 22:50 ` [PATCH v2 1/1] " J. German Rivera
2015-02-26 14:25 ` Alexander Graf [this message]
2015-02-26 14:30 ` Alexander Graf
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=54EF2CD6.2050608@suse.de \
--to=agraf@suse.de \
--cc=Geoff.Thorpe@freescale.com \
--cc=German.Rivera@freescale.com \
--cc=Kim.Phillips@freescale.com \
--cc=R89243@freescale.com \
--cc=arnd@arndb.de \
--cc=bhamciu1@freescale.com \
--cc=bhupesh.sharma@freescale.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nir.erez@freescale.com \
--cc=richard.schmitt@freescale.com \
--cc=scottwood@freescale.com \
--cc=stuart.yoder@freescale.com \
/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