From: John Stultz <john.stultz@linaro.org>
To: lkml <linux-kernel@vger.kernel.org>
Cc: John Stultz <john.stultz@linaro.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Jim Cromie <jim.cromie@gmail.com>,
Ralf Baechle <ralf@linux-mips.org>,
Yong Zhang <yong.zhang0@gmail.com>
Subject: [RFC][PATCH 0/3] Last of the clocksource_register_hz cleanups
Date: Mon, 23 Jan 2012 16:05:47 -0800 [thread overview]
Message-ID: <1327363550-19952-1-git-send-email-john.stultz@linaro.org> (raw)
So I'm hoping to finally kill off clocksource_register(), so I wanted
to get the last of the hardware specific clocksources changes that I
cannot test to be reviewed by maintainers.
In some cases the patches are not clearly correct, or the existing
code is broken and I don't know how to fix it. So feedback here
would be greatly appreciated!
thanks
-john
CC: Martin Schwidefsky <schwidefsky@de.ibm.com>
CC: Jim Cromie <jim.cromie@gmail.com>
CC: Ralf Baechle <ralf@linux-mips.org>
CC: Yong Zhang <yong.zhang0@gmail.com>
John Stultz (3):
clocksource: s390: Convert s390 to use clocksource_register_khz
clocksource: scx200_hrt: Convert scx200 to use
clocksource_register_hz
clocksource: Convert mips pnx8550 to use clocksource_register_hz
arch/mips/pnx8550/common/time.c | 7 ++++++-
arch/s390/kernel/time.c | 13 ++++++++++---
drivers/clocksource/scx200_hrt.c | 19 ++++++-------------
3 files changed, 22 insertions(+), 17 deletions(-)
--
1.7.3.2.146.gca209
next reply other threads:[~2012-01-24 0:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 0:05 John Stultz [this message]
2012-01-24 0:05 ` [RFC][PATCH 1/3] clocksource: s390: Convert s390 to use clocksource_register_khz John Stultz
2012-01-24 0:05 ` [RFC][PATCH 2/3] clocksource: scx200_hrt: Convert scx200 to use clocksource_register_hz John Stultz
2012-01-24 18:53 ` Jim Cromie
2012-01-24 23:00 ` John Stultz
2012-01-24 23:51 ` Jim Cromie
2012-01-25 0:14 ` John Stultz
2012-01-24 0:05 ` [PATCH 3/3] clocksource: Convert mips pnx8550 " John Stultz
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=1327363550-19952-1-git-send-email-john.stultz@linaro.org \
--to=john.stultz@linaro.org \
--cc=jim.cromie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=schwidefsky@de.ibm.com \
--cc=yong.zhang0@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome