From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [GIT PULL 2/3] omap timer changes for v3.10 merge window
Date: Mon, 8 Apr 2013 10:46:49 -0700 [thread overview]
Message-ID: <20130408174648.GS10155@atomide.com> (raw)
In-Reply-To: <201304081940.12773.arnd@arndb.de>
* Arnd Bergmann <arnd@arndb.de> [130408 10:45]:
> On Thursday 04 April 2013, Tony Lindgren wrote:
> > arch/arm/mach-omap2/board-cm-t3517.c | 2 +-
> > arch/arm/mach-omap2/board-generic.c | 2 +-
> > arch/arm/mach-omap2/common.h | 3 +-
> > arch/arm/mach-omap2/timer.c | 124 ++++++++++++++++++-----------------
> > 4 files changed, 66 insertions(+), 65 deletions(-)
>
> BTW, do you have any plans to move the timer.c file to drivers/clocksource?
>
> I think that's where most of them are heading now.
Yes that's the plan.
With the various patches posted at least the timer code
GPMC code should be very close to being movable. And the
mailbox code is getting moved to drivers based on the pull
request I saw for that few days ago.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/3] omap timer changes for v3.10 merge window
Date: Mon, 8 Apr 2013 10:46:49 -0700 [thread overview]
Message-ID: <20130408174648.GS10155@atomide.com> (raw)
In-Reply-To: <201304081940.12773.arnd@arndb.de>
* Arnd Bergmann <arnd@arndb.de> [130408 10:45]:
> On Thursday 04 April 2013, Tony Lindgren wrote:
> > arch/arm/mach-omap2/board-cm-t3517.c | 2 +-
> > arch/arm/mach-omap2/board-generic.c | 2 +-
> > arch/arm/mach-omap2/common.h | 3 +-
> > arch/arm/mach-omap2/timer.c | 124 ++++++++++++++++++-----------------
> > 4 files changed, 66 insertions(+), 65 deletions(-)
>
> BTW, do you have any plans to move the timer.c file to drivers/clocksource?
>
> I think that's where most of them are heading now.
Yes that's the plan.
With the various patches posted at least the timer code
GPMC code should be very close to being movable. And the
mailbox code is getting moved to drivers based on the pull
request I saw for that few days ago.
Regards,
Tony
next prev parent reply other threads:[~2013-04-08 17:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0LdWUM-1V6HSB0nzO-00i0Xm@mx.kundenserver.de>
2013-04-08 17:36 ` [GIT PULL 2/3] omap timer changes for v3.10 merge window Arnd Bergmann
2013-04-08 17:36 ` Arnd Bergmann
2013-04-08 17:52 ` Tony Lindgren
2013-04-08 17:52 ` Tony Lindgren
2013-04-08 17:40 ` Arnd Bergmann
2013-04-08 17:40 ` Arnd Bergmann
2013-04-08 17:46 ` Tony Lindgren [this message]
2013-04-08 17:46 ` Tony Lindgren
2013-04-04 19:39 [GIT PULL 1/3] omap usb platform init " Tony Lindgren
2013-04-04 19:39 ` [GIT PULL 2/3] omap timer " Tony Lindgren
2013-04-04 19:39 ` 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=20130408174648.GS10155@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
/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.