Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Thu, 18 Apr 2019 11:07:14 +0200 (CEST)
From:   Thomas Gleixner <tglx@linutronix.de>
To:     Miroslav Lichvar <mlichvar@redhat.com>
cc:     Ondrej Mosnacek <omosnace@redhat.com>,
        Linux kernel mailing list <linux-kernel@vger.kernel.org>,
        John Stultz <john.stultz@linaro.org>,
        Richard Cochran <richardcochran@gmail.com>,
        Prarit Bhargava <prarit@redhat.com>
Subject: Re: [PATCH] ntp: Allow TAI-UTC offset to be set to zero
In-Reply-To: <20190418080710.GE5984@localhost>
Message-ID: <alpine.DEB.2.21.1904181106150.3174@nanos.tec.linutronix.de>
References: <20190417084833.7401-1-mlichvar@redhat.com> <CAFqZXNu_pc1BEGZJb=3Ez58uN+BfoECpSm2yVqv1MMx7iTLfRw@mail.gmail.com> <20190418080710.GE5984@localhost>
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, 18 Apr 2019, Miroslav Lichvar wrote:
> On Wed, Apr 17, 2019 at 11:00:23AM +0200, Ondrej Mosnacek wrote:
> > On Wed, Apr 17, 2019 at 10:48 AM Miroslav Lichvar <mlichvar@redhat.com> wrote:
> > > Change the ADJ_TAI check to accept zero as a valid TAI-UTC offset in
> > > order to allow setting it back to the initial value.
> 
> > Thanks for sending the patch! Maybe you (or the committer) could
> > consider adding:
> > 
> > Fixes: 153b5d054ac2 ("ntp: support for TAI")
> 
> To me the change looks more like an extension of the API, rather than
> a bug fix, so I'd leave that up to the committer.

I don't see why we need to backport that all the way, but I'm happy to add
the tag if there is some really good reason.

Thanks,

	tglx