From: Matthias Kaehlcke <mka@chromium.org>
To: Dmitry Torokhov <dtor@chromium.org>
Cc: John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Grant Grundler <grundler@chromium.org>,
Greg Hackmann <ghackmann@google.com>,
Michael Davidson <md@google.com>
Subject: Re: [PATCH] clocksource: Use GENMASK_ULL in definition of CLOCKSOURCE_MASK
Date: Mon, 17 Apr 2017 09:57:04 -0700 [thread overview]
Message-ID: <20170417165704.GO28657@google.com> (raw)
In-Reply-To: <CAE_wzQ-+qZAAwEzQDwUZiBnZuy-S5uPauHy9U0Oxzwqko_C+dg@mail.gmail.com>
Hi Dmitry,
El Fri, Apr 14, 2017 at 09:02:03PM -0700 Dmitry Torokhov ha dit:
> On Tue, Apr 11, 2017 at 12:17 PM, Matthias Kaehlcke <mka@chromium.org> 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>
> > ---
> > 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..06e604b9e9dc 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) (u64)GENMASK_ULL((bits) - 1, 0)
>
> I do not think cast to u64 is needed for GENMASK_ULL.
Indeed, it is not needed, I will update the patch
Thanks!
Matthias
prev parent reply other threads:[~2017-04-17 16:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 19:17 [PATCH] clocksource: Use GENMASK_ULL in definition of CLOCKSOURCE_MASK Matthias Kaehlcke
2017-04-15 4:02 ` Dmitry Torokhov
2017-04-17 16:57 ` Matthias Kaehlcke [this message]
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=20170417165704.GO28657@google.com \
--to=mka@chromium.org \
--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=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 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.