From: jic23@cam.ac.uk (Jonathan Cameron)
To: linux-arm-kernel@lists.infradead.org
Subject: Update: ARM Sub-Architecture Maintainers workshop at Kernel Summit 2011
Date: Thu, 20 Oct 2011 14:48:53 +0100 [thread overview]
Message-ID: <4EA026C5.1050803@cam.ac.uk> (raw)
In-Reply-To: <CACRpkdawG9aKAT7PHuYapiHexkteq-_seQGd6iRORyt-LwbmxA@mail.gmail.com>
On 10/20/11 14:35, Linus Walleij wrote:
> On Tue, Aug 30, 2011 at 8:00 AM, Grant Likely <grant.likely@secretlab.ca> 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
next prev parent reply other threads:[~2011-10-20 13:48 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 6:00 Update: ARM Sub-Architecture Maintainers workshop at Kernel Summit 2011 Grant Likely
2011-08-30 6:27 ` Igor Grinberg
2011-08-30 13:44 ` Grant Likely
2011-08-30 14:00 ` Igor Grinberg
2011-08-30 19:17 ` [Ksummit-2011-discuss] " Chris Ball
2011-08-30 12:55 ` Nicolas Ferre
2011-08-30 13:56 ` Wolfram Sang
2011-08-30 14:42 ` David Brown
2011-08-30 16:58 ` Paul Walmsley
2011-08-30 19:51 ` Olof Johansson
2011-08-30 23:42 ` Stephen Warren
2011-08-31 5:50 ` Marek Szyprowski
2011-08-30 23:10 ` Pavel Machek
2011-08-31 1:29 ` Marek Vasut
2011-08-31 2:31 ` Bryan Wu
2011-08-31 2:58 ` Marek Vasut
2011-08-31 3:07 ` Bryan Wu
2011-08-31 18:57 ` Grant Likely
2011-08-31 2:57 ` Bryan Wu
2011-08-31 2:59 ` Marek Vasut
2011-08-31 3:08 ` Bryan Wu
2011-08-31 4:01 ` Marek Vasut
2011-08-31 5:52 ` Eric Miao
2011-08-31 15:15 ` Marc Zyngier
2011-09-27 13:25 ` Igor Grinberg
2011-10-12 9:14 ` Igor Grinberg
2011-10-12 9:19 ` Catalin Marinas
2011-10-17 17:36 ` Igor Grinberg
2011-10-12 15:33 ` Nicolas Pitre
2011-10-17 17:31 ` Igor Grinberg
2011-10-12 10:01 ` Catalin Marinas
2011-10-12 15:00 ` Nicolas Pitre
2011-10-17 8:54 ` Catalin Marinas
2011-10-17 10:56 ` Marek Vasut
2011-10-20 13:35 ` Linus Walleij
2011-10-20 13:48 ` Jonathan Cameron [this message]
2011-10-20 14:25 ` Barry Song
2011-10-20 14:46 ` Mark Brown
2011-10-20 14:55 ` Jonathan Cameron
2011-10-21 9:39 ` Barry Song
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=4EA026C5.1050803@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=linux-arm-kernel@lists.infradead.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).