All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Pavel Machek <pavel@ucw.cz>, Stephen Boyd <sboyd@codeaurora.org>
Cc: linux-kernel@vger.kernel.org, will.deacon@arm.com,
	catalin.marinas@arm.com, olof@lixom.net,
	sudeep.karkadanagesha@arm.com
Subject: Re: [PATCH] drivers: clocksource: Hide arm_arch_timer eventstream Kconfig on non-ARM
Date: Wed, 20 Nov 2013 22:16:20 +0100	[thread overview]
Message-ID: <528D26A4.4010600@linaro.org> (raw)
In-Reply-To: <20131120210931.GA1782@amd.pavel.ucw.cz>

On 11/20/2013 10:09 PM, Pavel Machek wrote:
> On Wed 2013-11-20 12:02:03, Stephen Boyd wrote:
>> Pavel Machek reports that this config is exposed on x86 where the
>> ARM architected timers aren't even present. Make it depend on the
>> ARM architected timers being selected so that non-ARM builds
>> aren't asked about it.
>>
>> Reported-by: Pavel Machek <pavel@ucw.cz>
>> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
>
> Reviewed-by: Pavel Machek <pavel@ucw.cz>
>
> Thanks!

Applied to my tree as a 3.13 fix.

Thanks Stephen and Pavel !

   -- Daniel

-- 
  <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog


  reply	other threads:[~2013-11-20 21:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20 19:21 Support for ARM architected timer event stream generation on x86 Pavel Machek
2013-11-20 20:02 ` [PATCH] drivers: clocksource: Hide arm_arch_timer eventstream Kconfig on non-ARM Stephen Boyd
2013-11-20 21:09   ` Pavel Machek
2013-11-20 21:16     ` Daniel Lezcano [this message]
2013-11-21  9:20   ` Takashi Iwai

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=528D26A4.4010600@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=pavel@ucw.cz \
    --cc=sboyd@codeaurora.org \
    --cc=sudeep.karkadanagesha@arm.com \
    --cc=will.deacon@arm.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 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.