From: john.stultz@linaro.org (John Stultz)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] clockevent driver cleanup for 3.9
Date: Thu, 10 Jan 2013 11:01:57 -0800 [thread overview]
Message-ID: <50EF1025.9030101@linaro.org> (raw)
In-Reply-To: <20130110124132.GA8680@S2101-09.ap.freescale.net>
On 01/10/2013 04:41 AM, Shawn Guo wrote:
> The following changes since commit a49f0d1ea3ec94fc7cf33a7c36a16343b74bd565:
>
> Linux 3.8-rc1 (2012-12-21 17:19:00 -0800)
>
> are available in the git repository at:
>
> git://git.linaro.org/people/shawnguo/linux-2.6.git tags/clean-clkevt-3.9
>
> for you to fetch changes up to ab8e73c98749a58c242b187c9799db70cd903157:
>
> clocksource: use clockevents_config_and_register() where possible (2013-01-10 20:24:30 +0800)
>
> ----------------------------------------------------------------
> As John has showed zero interest to collect clock event driver patches,
> I send both patches through arm-soc tree here.
So ack on it going through the arm-soc tree. I do appreciate the effort
in making these cleanups!
And to be clear, its not just a matter of my not having interest, but
more an issue of me wanting the patches to be merged where they are most
likely to be reviewed and tested by folks who know and have the
hardware. Even when I've made changes in the clocksource core, and had
to do similar cleanups across the various architectures, I worked to
push my patches through the arch trees (even when it takes months upon
months to get them merged), since I don't want to blindside anyone.
thanks
-john
next prev parent reply other threads:[~2013-01-10 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 12:41 [GIT PULL] clockevent driver cleanup for 3.9 Shawn Guo
2013-01-10 16:43 ` Stephen Warren
2013-01-10 19:01 ` John Stultz [this message]
2013-01-11 13:47 ` Shawn Guo
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=50EF1025.9030101@linaro.org \
--to=john.stultz@linaro.org \
--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).