All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miroslav Lichvar <mlichvar@redhat.com>
To: John Stultz <john.stultz@linaro.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Richard Cochran <richardcochran@gmail.com>,
	Prarit Bhargava <prarit@redhat.com>
Subject: Re: [PATCHv1] timekeeping: Update multiplier when NTP frequency is set directly
Date: Mon, 4 Jun 2018 12:17:41 +0200	[thread overview]
Message-ID: <20180604101741.GB27828@localhost> (raw)
In-Reply-To: <CALAqxLWV2d6yTeAK7j31Nvu33TqLmPLNDvzzSu0TSnDEUhVc1A@mail.gmail.com>

On Tue, May 29, 2018 at 10:42:05AM -0700, John Stultz wrote:
> On Tue, May 29, 2018 at 3:53 AM, Miroslav Lichvar <mlichvar@redhat.com> wrote:
> > -void update_wall_time(void)
> > +static void timekeeping_advance(bool force_update)
> 
> This is kind of a nit, but mind switching out bool for an enum?  Using
> something like TK_ADV_NORMAL and TK_ADV_FORCE?
> 
> > +void update_wall_time(void)
> > +{
> > +       timekeeping_advance(false);
> > +}
> 
> The enum makes usage like timekeeping_advance(false) a little less
> opaque to the reader ("Wait, don't advance? Let me go look at the
> function").
> 
> We got bitten by this earlier when we had the old
> "timekeeping_update(tk, true, false, true)" usage.

Ok. That make sense. I'll send a v2.

Thanks,

-- 
Miroslav Lichvar

      reply	other threads:[~2018-06-04 10:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29 10:53 [PATCHv1] timekeeping: Update multiplier when NTP frequency is set directly Miroslav Lichvar
2018-05-29 17:42 ` John Stultz
2018-06-04 10:17   ` Miroslav Lichvar [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=20180604101741.GB27828@localhost \
    --to=mlichvar@redhat.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prarit@redhat.com \
    --cc=richardcochran@gmail.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.