linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@redhat.com>
Cc: linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org,
	x86@kernel.org, hpa@zytor.com,
	Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH 0/5] X86: Migrate clockevent drivers to 'set-state' interface
Date: Thu, 16 Jul 2015 16:28:43 +0530	[thread overview]
Message-ID: <cover.1437042675.git.viresh.kumar@linaro.org> (raw)

Hi Thomas/Ingo,

This series migrates x86 architecture clockevent drivers to the new
set-state interface. This would enable these drivers to use new states
(like: ONESHOT_STOPPED, etc.) of a clockevent device (if required), as
the set-mode interface is marked obsolete now and wouldn't be expanded
to handle new states.

Rebased over: v4.2-rc2
Target kernel: v4.3

This has been build/boot tested by two bots for few days now.

- kernelci, http://kernelci.org/
- 0-DAY kernel test infrastructure, kbuild test robot

Viresh Kumar (5):
  x86/apic: Migrate to new 'set-state' interface
  x86/hpet: Migrate to new 'set-state' interface
  x86/lguest/timer: Migrate to new 'set-state' interface
  x86/uv/time: Migrate to new 'set-state' interface
  x86/xen/time: Migrate to new 'set-state' interface

 arch/x86/kernel/apic/apic.c    |  86 ++++++++++--------
 arch/x86/kernel/hpet.c         | 198 ++++++++++++++++++++++++++---------------
 arch/x86/lguest/boot.c         |  24 ++---
 arch/x86/platform/uv/uv_time.c |  37 +++-----
 arch/x86/xen/time.c            |  63 +++++--------
 5 files changed, 217 insertions(+), 191 deletions(-)

-- 
2.4.0


             reply	other threads:[~2015-07-16 10:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16 10:58 Viresh Kumar [this message]
2015-07-16 10:58 ` [PATCH 1/5] x86/apic: Migrate to new 'set-state' interface Viresh Kumar
2015-07-30 19:27   ` [tip:x86/apic] x86/apic: Migrate apic timer to new set_state interface tip-bot for Viresh Kumar
2015-07-16 10:58 ` [PATCH 2/5] x86/hpet: Migrate to new 'set-state' interface Viresh Kumar
2015-07-30 19:30   ` [tip:x86/core] x86/hpet: Migrate to new set_state interface tip-bot for Viresh Kumar
2015-07-16 10:58 ` [PATCH 3/5] x86/lguest/timer: Migrate to new 'set-state' interface Viresh Kumar
2015-07-16 11:59   ` Rusty Russell
2015-07-30 19:28   ` [tip:x86/platform] x86/lguest/timer: Migrate to new set-state interface tip-bot for Viresh Kumar
2015-07-16 10:58 ` [PATCH 4/5] x86/uv/time: Migrate to new 'set-state' interface Viresh Kumar
2015-07-30 19:28   ` [tip:x86/platform] x86/uv/time: Migrate to new set-state interface tip-bot for Viresh Kumar
2015-07-30 20:04     ` Christoph Lameter
2015-07-30 22:25       ` Thomas Gleixner
2015-07-31  5:21       ` Viresh Kumar
2015-07-31 12:20         ` Dimitri Sivanich
2015-08-04 15:25           ` Nathan Zimmer
2015-08-05  5:15             ` Viresh Kumar
2015-08-05 14:29               ` Nathan Zimmer
2015-07-16 10:58 ` [PATCH 5/5] x86/xen/time: Migrate to new 'set-state' interface Viresh Kumar
2015-07-30 19:28   ` [tip:x86/platform] x86/xen/time: Migrate to new set-state interface tip-bot for Viresh Kumar

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=cover.1437042675.git.viresh.kumar@linaro.org \
    --to=viresh.kumar@linaro.org \
    --cc=hpa@zytor.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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).