public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PULL] clockevents: a couple of fixes for tip/timers/urgent
Date: Fri, 7 Aug 2015 09:19:47 +0200	[thread overview]
Message-ID: <20150807071947.GB23817@gmail.com> (raw)
In-Reply-To: <55C37D4A.6000302@linaro.org>


* Daniel Lezcano <daniel.lezcano@linaro.org> wrote:

> 
> Hi Ingo,
> 
> this pull request contains the following changes:
> 
>  - Prevented to suspend or resume the sh_cmt clocksource when this one is
> not enabled (Geert Uytterhoeven)
>  - Improved build coverage with COMPILE_TEST for the stm32 timer (Maxime
> Coquelin)
> 
> Thanks !
> 
>   -- Daniel
> 
> The following changes since commit 0f44705175347ec96935d60b765b5d14ecc763bb:
> 
>   tick: Move the export of tick_broadcast_oneshot_control to the proper
> place (2015-07-14 12:01:04 +0200)
> 
> are available in the git repository at:
> 
>   http://git.linaro.org/people/daniel.lezcano/linux.git
> clockevents/4.2-fixes
> 
> for you to fetch changes up to 1822a48be12f7ce2799d3423e49b967896794c4d:
> 
>   clockevents/drivers/sh_cmt: Only perform clocksource suspend/resume if
> enabled (2015-08-06 17:17:20 +0200)
> 
> ----------------------------------------------------------------
> Geert Uytterhoeven (1):
>       clockevents/drivers/sh_cmt: Only perform clocksource suspend/resume if
> enabled
> 
> Maxime Coquelin (1):
>       clockevents/drivers/timer-stm32: Improve dependencies of timer-stm32
> 
>  drivers/clocksource/Kconfig  | 4 ++--

Hm, so why is this an urgent fix, i.e. a regression fix? It appears to widen build 
coverage:

 config CLKSRC_STM32
-       bool "Clocksource for STM32 SoCs" if !ARCH_STM32
-       depends on OF && ARM && (ARCH_STM32 || COMPILE_TEST)
+       bool "Clocksource for STM32 SoCs" if COMPILE_TEST
+       depends on OF && GENERIC_CLOCKEVENTS

that can at most introduce build regressions - not fix anything.

If there's any other purpose of this change it's not mentioned in the changelog.

Also, I think the change is broken to begin with:

+       bool "Clocksource for STM32 SoCs" if COMPILE_TEST

this will turn off the driver even in its target platform!

The right way to increase testing this way is via:

	depends on ... || COMPILE_TEST

Thanks,

	Ingo

  parent reply	other threads:[~2015-08-07  7:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06 15:29 [PULL] clockevents: a couple of fixes for tip/timers/urgent Daniel Lezcano
2015-08-06 15:32 ` [PATCH 1/2] clockevents/drivers/timer-stm32: Improve dependencies of timer-stm32 Daniel Lezcano
2015-08-06 15:32   ` [PATCH 2/2] clockevents/drivers/sh_cmt: Only perform clocksource suspend/resume if enabled Daniel Lezcano
2015-08-09 10:25     ` [tip:timers/urgent] " tip-bot for Geert Uytterhoeven
2015-08-07  7:19 ` Ingo Molnar [this message]
2015-08-07 21:25   ` [PULL] clockevents: a couple of fixes for tip/timers/urgent Geert Uytterhoeven

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=20150807071947.GB23817@gmail.com \
    --to=mingo@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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