linux-kernel - Re: [PATCH v2 1/1] drivers/bus: fsl-mc object allocator driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <54EF2CD6.2050608@suse.de>
Date:	Thu, 26 Feb 2015 15:25:26 +0100
From:	Alexander Graf <agraf@...e.de>
To:	"J. German Rivera" <German.Rivera@...escale.com>,
	gregkh@...uxfoundation.org, arnd@...db.de,
	linux-kernel@...r.kernel.org
CC:	stuart.yoder@...escale.com, Kim.Phillips@...escale.com,
	scottwood@...escale.com, bhamciu1@...escale.com,
	R89243@...escale.com, Geoff.Thorpe@...escale.com,
	bhupesh.sharma@...escale.com, nir.erez@...escale.com,
	richard.schmitt@...escale.com
Subject: Re: [PATCH v2 1/1] drivers/bus: fsl-mc object allocator driver

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/