From: Ingo Molnar <mingo@kernel.org>
To: John Stultz <john.stultz@linaro.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] time/ntp fix
Date: Sat, 21 Feb 2015 06:49:02 +0100 [thread overview]
Message-ID: <20150221054901.GA21071@gmail.com> (raw)
In-Reply-To: <CALAqxLW0MNjj8aLiMHB+i2=4JwETX=KGmK154wnoz2ENmT6dsg@mail.gmail.com>
* John Stultz <john.stultz@linaro.org> wrote:
> On Fri, Feb 20, 2015 at 2:26 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> > On Fri, Feb 20, 2015 at 5:44 AM, Ingo Molnar <mingo@kernel.org> wrote:
> >>
> >> John Stultz (1):
> >> ntp: Fixup adjtimex freq validation on 32-bit systems
> >
> > This is confusing. 32-bit?
>
> Right, so the check that was added in a previous commit
> is really only a concern for 64bit systems, but was
> applied to both 32 and 64bit systems, which results in
> breaking 32bit systems.
>
> Thus the "fix" here is to make the check only apply to
> 64bit systems.
Yeah, perhaps a better commit title would have been to
write:
time/ntp: Fix adjtimex freq validation code build warning on 32-bit systems
To make it clear that the problem fixed is a 32-bit
warning, and that the fix for that is to only check on
64-bit systems.
I agreed with your BITS_PER_LONG check when I reviewed your
patch, people usually do an ugly #ifdef, I think this
in line check form is nicer.
Thanks,
Ingo
next prev parent reply other threads:[~2015-02-21 5:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 13:44 [GIT PULL] time/ntp fix Ingo Molnar
2015-02-20 16:15 ` Dongsheng Song
2015-02-20 22:26 ` Linus Torvalds
2015-02-20 22:58 ` John Stultz
2015-02-20 23:16 ` Linus Torvalds
2015-02-21 5:49 ` Ingo Molnar [this message]
2015-02-22 20:29 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2012-07-18 8:45 Ingo Molnar
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=20150221054901.GA21071@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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