mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: John Stultz <john.stultz@linaro.org>,
	linux-kernel@vger.kernel.org, Dmitry Torokhov <dtor@chromium.org>,
	Grant Grundler <grundler@chromium.org>,
	Greg Hackmann <ghackmann@google.com>,
	Michael Davidson <md@google.com>
Subject: Re: [PATCH v2] clocksource: Use GENMASK_ULL in definition of CLOCKSOURCE_MASK
Date: Tue, 18 Apr 2017 10:13:34 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1704181012240.1659@nanos> (raw)
In-Reply-To: <20170417173900.27425-1-mka@chromium.org>

On Mon, 17 Apr 2017, Matthias Kaehlcke wrote:
> Besides reusing existing code this removes the special case handling
> for 64-bit masks, which causes clang to raise a shift count overflow
> warning due to https://bugs.llvm.org//show_bug.cgi?id=10030.
> 
> Suggested-by: Dmitry Torokhov <dtor@chromium.org>
> Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
> ---
> Changes in v2:
> - Remove unnecessary cast to u64
> 
>  include/linux/clocksource.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/linux/clocksource.h b/include/linux/clocksource.h
> index cfc75848a35d..f2b10d9ebd04 100644
> --- a/include/linux/clocksource.h
> +++ b/include/linux/clocksource.h
> @@ -120,7 +120,7 @@ struct clocksource {
> #define CLOCK_SOURCE_RESELECT			0x100
>  
>  /* simplify initialization of mask field */
> -#define CLOCKSOURCE_MASK(bits) (u64)((bits) < 64 ? ((1ULL<<(bits))-1) : -1)
> +#define CLOCKSOURCE_MASK(bits) GENMASK_ULL((bits) - 1, 0)
>  
>  static inline u32 clocksource_freq2mult(u32 freq, u32 shift_constant, u64 from)
>  {
> -- 
> 2.12.2.762.g0e3151a226-goog

Neither patch nor git-am can apply that patch. Please fix your tools.

Thanks,

	tglx

  reply	other threads:[~2017-04-18  8:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-17 17:38 Matthias Kaehlcke
2017-04-18  8:13 ` Thomas Gleixner [this message]
2017-04-18 23:30 Matthias Kaehlcke

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=alpine.DEB.2.20.1704181012240.1659@nanos \
    --to=tglx@linutronix.de \
    --cc=dtor@chromium.org \
    --cc=ghackmann@google.com \
    --cc=grundler@chromium.org \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=md@google.com \
    --cc=mka@chromium.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

all inboxes | Powered by JetHome®