linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mingo@kernel.org (Ingo Molnar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clockevents: Add (missing) default case for switch blocks
Date: Fri, 20 Feb 2015 12:41:36 +0100	[thread overview]
Message-ID: <20150220114136.GA27483@gmail.com> (raw)
In-Reply-To: <20150220113753.GP5029@twins.programming.kicks-ass.net>


* Peter Zijlstra <peterz@infradead.org> wrote:

> On Fri, Feb 20, 2015 at 10:36:59AM +0100, Ingo Molnar wrote:

> > > But it does mean we need to be able to add values to 
> > > the enum.
> > 
> > So I'm confused: if we are using proper callbacks (like 
> > my example outlined) , why is a 'mode enum' needed at 
> > all?
> 
> Ah, its because the enum is shared between two different 
> use-cases. The one is the clockevent driver for the 
> clock_event_device::set_mode() call, and one is the 
> clockevent core call: clockevent_set_mode().
> 
> The previous patch changed the driver interface, but 
> retained the sharing of the enum across both interfaces.
> 
> Maybe we should break that enum into two; one for devices 
> and one for the core interface and avoid the problem that 
> way.

Yeah, that would do the trick.

Thanks,

	Ingo

  reply	other threads:[~2015-02-20 11:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20  6:32 [PATCH] clockevents: Add (missing) default case for switch blocks Viresh Kumar
2015-02-20  8:38 ` Ingo Molnar
2015-02-20  8:48   ` Peter Zijlstra
2015-02-20  9:36     ` Ingo Molnar
2015-02-20 10:12       ` Viresh Kumar
2015-02-20 10:52         ` Ingo Molnar
2015-02-20 11:37       ` Peter Zijlstra
2015-02-20 11:41         ` Ingo Molnar [this message]
2015-02-20 11:56           ` Viresh Kumar
2015-02-20 13:22             ` Ingo Molnar
2015-02-20 13:58               ` Viresh Kumar
2015-02-20 14:04                 ` Ingo Molnar
2015-02-23  5:33                   ` Viresh Kumar
2015-02-23 16:37                     ` Ingo Molnar
2015-02-24 11:11                       ` viresh kumar
2015-02-24 14:54                         ` Ingo Molnar
2015-02-24 15:12                           ` 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=20150220114136.GA27483@gmail.com \
    --to=mingo@kernel.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).