From mboxrd@z Thu Jan 1 00:00:00 1970 From: jic23@cam.ac.uk (Jonathan Cameron) Date: Thu, 20 Oct 2011 14:48:53 +0100 Subject: Update: ARM Sub-Architecture Maintainers workshop at Kernel Summit 2011 In-Reply-To: References: Message-ID: <4EA026C5.1050803@cam.ac.uk> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 10/20/11 14:35, Linus Walleij wrote: > On Tue, Aug 30, 2011 at 8:00 AM, Grant Likely wrote: > >> Nominates, but haven't responded personally: >> (...) >> 22) Linus Walleji > > I won't be coming, sorry friends. > >> Agenda proposals (Thanks to Nicolas and Olof): >> - the pin mux subsystem from linusw (especially if it is still RFC by >> then) > > I will be happy to attend by wire if provided the necessary details. > pin control with mux basics is in -next and I am iterating next design > step with Stephen Warren from nVidia. > >> Still accepting more proposals. Send me the topics you are burning to discuss. > > Since I'm not coming I don't know how relevant my opinions are. > > But a topic which I think is important is: > "Subsystems! Subsystems! Subsystems!" > (Bonus if you get Greg to shout this dancing on stage.) > > We have noticed a lack of subsystems such as pin control to > compartmentalize "stuff" currently stacking up in arch/arm/* > drivers/misc/* and drivers/mfd/*. > > The problem of how to adress this the proper way by creating > new subsystems need to be shed some light upon, just telling > every subarch to "go create a new subsystem, it'll just take a > few man-years of your working hours" apparently does not always > work. > > On a related key is the need to get the stuff in drivers/staging/iio > into drivers/ proper. Thanks Linus. What this needs is a few of those man hours of people ripping the proposed patches to shreds. Lots more to follow once step one is cleaned up :) > > Just my ?0.01.. > > BR, > Linus Walleij