From: Arnd Bergmann <arnd@arndb.de>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [GIT PULL] dmtimer changes for v3.2 merge window
Date: Fri, 30 Sep 2011 22:52:50 +0200 [thread overview]
Message-ID: <201109302252.50174.arnd@arndb.de> (raw)
In-Reply-To: <20110930204319.GM6324@atomide.com>
On Friday 30 September 2011, Tony Lindgren wrote:
> How about a branch called driver?
>
> There are still lots of pieces of code under arch/arm that should
> be eventually moved to live under drivers. For example the mux
> code and most of PM code can eventually be under drivers.
Yes, good idea! For the omap/voltage series, I currently plan to
group that with pm changes for that I got for the other socs
this time, but if there was less of it, that could also be drivers.
> But before that can be done some preparation is often needed,
> the actual move to live under drivers should be handled then
> by the driver and subsystem maintainers.
I think in some cases we first need to nominate a subsystem
maintainer who can take the drivers, but that's a different
issue.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] dmtimer changes for v3.2 merge window
Date: Fri, 30 Sep 2011 22:52:50 +0200 [thread overview]
Message-ID: <201109302252.50174.arnd@arndb.de> (raw)
In-Reply-To: <20110930204319.GM6324@atomide.com>
On Friday 30 September 2011, Tony Lindgren wrote:
> How about a branch called driver?
>
> There are still lots of pieces of code under arch/arm that should
> be eventually moved to live under drivers. For example the mux
> code and most of PM code can eventually be under drivers.
Yes, good idea! For the omap/voltage series, I currently plan to
group that with pm changes for that I got for the other socs
this time, but if there was less of it, that could also be drivers.
> But before that can be done some preparation is often needed,
> the actual move to live under drivers should be handled then
> by the driver and subsystem maintainers.
I think in some cases we first need to nominate a subsystem
maintainer who can take the drivers, but that's a different
issue.
Arnd
next prev parent reply other threads:[~2011-09-30 20:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 22:02 [GIT PULL] dmtimer changes for v3.2 merge window Tony Lindgren
2011-09-28 22:02 ` Tony Lindgren
2011-09-30 20:13 ` Arnd Bergmann
2011-09-30 20:13 ` Arnd Bergmann
2011-09-30 20:43 ` Tony Lindgren
2011-09-30 20:43 ` Tony Lindgren
2011-09-30 20:52 ` Arnd Bergmann [this message]
2011-09-30 20:52 ` Arnd Bergmann
2011-10-01 16:45 ` Arnd Bergmann
2011-10-01 16:45 ` Arnd Bergmann
2011-10-04 0:07 ` Tony Lindgren
2011-10-04 0:07 ` Tony Lindgren
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=201109302252.50174.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.