From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Status of arch/arm in linux-next
Date: Fri, 22 Apr 2011 00:17:21 -0700 [thread overview]
Message-ID: <20110422071721.GC841@atomide.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1104211629300.24613@xanadu.home>
* Nicolas Pitre <nicolas.pitre@linaro.org> [110421 13:59]:
> On Thu, 21 Apr 2011, Dave Jones wrote:
>
> > On Tue, Apr 19, 2011 at 05:05:46PM +0100, Mark Brown wrote:
>
> > This is why I don't believe that moving this code from arch/ to drivers/
> > will change anything.
>
> That at least would have the property of gathering drivers together
> according to their _purpose_, irrespective of their implementation
> details. That's the case for all the other class of drivers already.
> Why would cpufreq drivers be different?
And drivers do have well defined standards, so that automatically prevents
people sneaking in spaghetti calls to platform specific code ;)
Tony
next prev parent reply other threads:[~2011-04-22 7:17 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 9:44 Status of arch/arm in linux-next Russell King - ARM Linux
2011-04-14 11:08 ` Tony Lindgren
2011-04-14 12:02 ` Russell King - ARM Linux
2011-04-14 12:31 ` Tony Lindgren
2011-04-14 14:20 ` Mark Brown
2011-04-14 14:26 ` Tony Lindgren
2011-04-14 14:31 ` Russell King - ARM Linux
2011-04-14 18:32 ` Mark Brown
2011-04-15 15:12 ` Grant Likely
2011-04-15 15:56 ` Russell King - ARM Linux
2011-04-15 16:10 ` Grant Likely
2011-04-16 8:28 ` Russell King - ARM Linux
2011-04-16 16:57 ` Mark Brown
2011-04-18 8:10 ` Tony Lindgren
2011-04-18 13:57 ` Mark Brown
2011-04-18 14:41 ` Tony Lindgren
2011-04-18 15:58 ` Mark Brown
2011-04-18 17:18 ` Russell King - ARM Linux
2011-04-18 20:23 ` Mark Brown
2011-04-18 21:40 ` Thomas Gleixner
2011-04-18 23:55 ` Mark Brown
2011-04-14 14:07 ` Mark Brown
2011-04-15 2:59 ` Nico Erfurth
2011-04-15 8:21 ` Nicolas Ferre
2011-04-15 13:13 ` Nico Erfurth
2011-04-15 1:16 ` Linus Walleij
2011-04-15 6:26 ` Tony Lindgren
2011-04-19 14:16 ` Arnd Bergmann
2011-04-19 14:50 ` Mark Brown
2011-04-19 14:55 ` Arnd Bergmann
2011-04-19 15:04 ` Mark Brown
2011-04-19 15:14 ` Linus Walleij
2011-04-19 16:01 ` Arnd Bergmann
2011-04-19 16:05 ` Mark Brown
2011-04-21 20:14 ` Dave Jones
2011-04-21 21:02 ` Nicolas Pitre
2011-04-22 7:17 ` Tony Lindgren [this message]
2011-04-26 14:05 ` Arnd Bergmann
2011-04-26 17:04 ` Rafael J. Wysocki
2011-04-26 18:15 ` Dave Jones
2011-04-29 20:15 ` Dave Jones
2011-04-30 0:05 ` Nicolas Pitre
2011-05-01 23:02 ` Jamie Lokier
2011-04-19 16:27 ` Dave Jones
2011-04-19 17:12 ` Arnd Bergmann
2011-04-20 6:36 ` Linus Walleij
2011-04-21 7:32 ` Linus Walleij
2011-04-21 8:25 ` Arnd Bergmann
2011-04-22 7:56 ` Linus Walleij
2011-04-22 11:46 ` Linus Walleij
2011-05-02 13:49 ` Samuel Ortiz
2011-05-02 19:21 ` Linus Walleij
2011-04-20 7:33 ` Tony Lindgren
2011-04-20 7:43 ` Arnd Bergmann
2011-04-15 14:30 ` Martin Guy
2011-04-15 15:50 ` Russell King - ARM Linux
2011-04-18 15:17 ` Alexey Zaytsev
2011-04-18 16:23 ` Linus Torvalds
2011-04-18 21:54 ` Alexey Zaytsev
2011-04-19 15:02 ` Linus Torvalds
2011-04-19 15:20 ` Jean-Christophe PLAGNIOL-VILLARD
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=20110422071721.GC841@atomide.com \
--to=tony@atomide.com \
--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).