From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: dw_apb_timer_of.c: remove parts that were picoxcell-specific
Date: Mon, 6 May 2013 23:24:16 +0200 [thread overview]
Message-ID: <201305062324.17080.arnd@arndb.de> (raw)
In-Reply-To: <20130506155304.GA6645@amd.pavel.ucw.cz>
On Monday 06 May 2013, Pavel Machek wrote:
> On Mon 2013-05-06 15:45:22, Arnd Bergmann wrote:
> > On Monday 06 May 2013, Pavel Machek wrote:
> > >
> > > Hi!
> > >
> > > Ping? Previous version was tested by Dinh, and this one is based on
> > > Jamie's updates, so I assume it is acceptable for him, too.
> > >
> > > It brings two platforms closer together, and makes time actually work
> > > on socfpga. It would be good to get it applied.
> >
> > Who should apply it? I guess it needs to go through arm-soc with all the
> > other clocksource changes already queued up there. Can we have an Ack
> > from Jamie and from the clocksource maintainers?
>
> Well, changes to arch/arm/mach-picoxcell are single line (and that's a
> cleanup of duplicate include).
The point is that Jamie had comments on the earlier version, so it would
be good to see his Ack on the current one.
> So I guess it should go through the timekeeping tree...?
I would prefer that, but we can also take it through arm-soc, it doesn't
really matter.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Pavel Machek <pavel@denx.de>, tglx@linutronix.de
Cc: Jamie Iles <jamie@jamieiles.com>,
dinguyen@altera.com, wd@denx.de,
linux-arm-kernel@lists.infradead.org, olof@lixom.net,
kernel list <linux-kernel@vger.kernel.org>,
john.stultz@linaro.org
Subject: Re: dw_apb_timer_of.c: remove parts that were picoxcell-specific
Date: Mon, 6 May 2013 23:24:16 +0200 [thread overview]
Message-ID: <201305062324.17080.arnd@arndb.de> (raw)
In-Reply-To: <20130506155304.GA6645@amd.pavel.ucw.cz>
On Monday 06 May 2013, Pavel Machek wrote:
> On Mon 2013-05-06 15:45:22, Arnd Bergmann wrote:
> > On Monday 06 May 2013, Pavel Machek wrote:
> > >
> > > Hi!
> > >
> > > Ping? Previous version was tested by Dinh, and this one is based on
> > > Jamie's updates, so I assume it is acceptable for him, too.
> > >
> > > It brings two platforms closer together, and makes time actually work
> > > on socfpga. It would be good to get it applied.
> >
> > Who should apply it? I guess it needs to go through arm-soc with all the
> > other clocksource changes already queued up there. Can we have an Ack
> > from Jamie and from the clocksource maintainers?
>
> Well, changes to arch/arm/mach-picoxcell are single line (and that's a
> cleanup of duplicate include).
The point is that Jamie had comments on the earlier version, so it would
be good to see his Ack on the current one.
> So I guess it should go through the timekeeping tree...?
I would prefer that, but we can also take it through arm-soc, it doesn't
really matter.
Arnd
next prev parent reply other threads:[~2013-05-06 21:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 12:14 dw_apb_timer_of.c: remove parts that were picoxcell-specific Pavel Machek
2013-04-26 12:14 ` Pavel Machek
2013-04-26 12:41 ` Jamie Iles
2013-04-26 12:41 ` Jamie Iles
2013-04-26 21:37 ` Pavel Machek
2013-04-26 21:37 ` Pavel Machek
2013-04-26 21:43 ` Pavel Machek
2013-04-26 21:43 ` Pavel Machek
2013-05-06 12:48 ` Pavel Machek
2013-05-06 12:48 ` Pavel Machek
2013-05-06 13:45 ` Arnd Bergmann
2013-05-06 13:45 ` Arnd Bergmann
2013-05-06 15:53 ` Pavel Machek
2013-05-06 15:53 ` Pavel Machek
2013-05-06 21:24 ` Arnd Bergmann [this message]
2013-05-06 21:24 ` Arnd Bergmann
2013-05-07 13:57 ` Pavel Machek
2013-05-07 13:57 ` Pavel Machek
2013-05-07 16:39 ` John Stultz
2013-05-07 16:39 ` John Stultz
2013-05-07 20:11 ` Pavel Machek
2013-05-07 20:11 ` Pavel Machek
2013-05-08 0:30 ` John Stultz
2013-05-08 0:30 ` John Stultz
2013-05-10 12:38 ` Pavel Machek
2013-05-10 12:38 ` Pavel Machek
2013-05-07 20:13 ` Pavel Machek
2013-05-07 20:13 ` Pavel Machek
2013-05-07 9:36 ` Jamie Iles
2013-05-07 9:36 ` Jamie Iles
-- strict thread matches above, loose matches on Subject: below --
2013-04-23 10:58 Pavel Machek
2013-04-24 22:44 ` Dinh Nguyen
2013-04-26 11:36 ` Pavel Machek
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=201305062324.17080.arnd@arndb.de \
--to=arnd@arndb.de \
--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 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.