From: Baolin Wang <baolin.wang@linaro.org>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Arnd Bergmann <arnd@arndb.de>, Mark Brown <broonie@kernel.org>,
linux-rtc@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND PATCH 1/3] rtc: Use time64_t to save range_max of RTC
Date: Thu, 8 Mar 2018 10:47:22 +0800 [thread overview]
Message-ID: <CAMz4kuKcLif02j6VwfAgQ1=4orhydboj9yXgvau=KQofkuosLA@mail.gmail.com> (raw)
In-Reply-To: <20180307225411.GA20370@piout.net>
Hi Alexandre,
On 8 March 2018 at 06:54, Alexandre Belloni
<alexandre.belloni@bootlin.com> wrote:
> Hi,
>
> On 26/02/2018 at 16:33:56 +0800, Baolin Wang wrote:
>> We need use rtc->range_max to valid if the time values are valid,
>> and the time values are saved by time64_t type. So change the
>> rtc->range_max to time64_t type for comparison correctly.
>>
>
> I'm not applying this one because the described issue will never happen
> as negative times are forbidden by the rtc subsystem.
OK.
>
> I've applied the two following patches
>
Thanks.
--
Baolin.wang
Best Regards
prev parent reply other threads:[~2018-03-08 2:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 8:33 [RESEND PATCH 1/3] rtc: Use time64_t to save range_max of RTC Baolin Wang
2018-02-26 8:33 ` [RESEND PATCH 2/3] rtc: Factor out the RTC range validation into rtc_valid_range() Baolin Wang
2018-02-26 8:33 ` [RESEND PATCH 3/3] rtc: Add one offset seconds to expand RTC range Baolin Wang
2018-03-07 22:54 ` [RESEND PATCH 1/3] rtc: Use time64_t to save range_max of RTC Alexandre Belloni
2018-03-08 2:47 ` Baolin Wang [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='CAMz4kuKcLif02j6VwfAgQ1=4orhydboj9yXgvau=KQofkuosLA@mail.gmail.com' \
--to=baolin.wang@linaro.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).