From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Dev Null <devnull@uvos.xyz>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Sebastian Reichel <sre@kernel.org>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-omap@vger.kernel.org, Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org, Merlijn Wajer <merlijn@wizzup.org>,
Tony Lindgren <tony@atomide.com>,
linux-rtc@vger.kernel.org,
"Sicelo A . Mhlongo" <absicsz@gmail.com>
Subject: Re: [PATCH] rtc: cpcap: fix range
Date: Thu, 2 Jul 2020 22:23:10 +0200 [thread overview]
Message-ID: <159372105822.57284.8366488507603282804.b4-ty@bootlin.com> (raw)
In-Reply-To: <20200629114123.27956-1-sebastian.reichel@collabora.com>
On Mon, 29 Jun 2020 13:41:23 +0200, Sebastian Reichel wrote:
> Unbreak CPCAP driver, which has one more bit in the day counter
> increasing the max. range from 2014 to 2058. The original commit
> introducing the range limit was obviously wrong, since the driver
> has only been written in 2017 (3 years after 14 bits would have
> run out).
Applied, thanks!
What happen is that I can't count bits and so I though PCAP had 13 bits and
CPCAP 14 bits while it is indeed 14 and 15. I did the correct thing in the PCAP
driver though.
Thanks for the fix!
[1/1] rtc: cpcap: fix range
commit: d6ac11f677ded28180fc9e59b01db79036c3ec31
Best regards,
--
Alexandre Belloni <alexandre.belloni@bootlin.com>
prev parent reply other threads:[~2020-07-02 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200629002917.0a2045380a0fe022f852e067@uvos.xyz>
2020-06-29 11:41 ` [PATCH] rtc: cpcap: fix range Sebastian Reichel
2020-06-29 14:34 ` Tony Lindgren
2020-06-29 17:25 ` Merlijn Wajer
2020-07-02 20:23 ` Alexandre Belloni [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=159372105822.57284.8366488507603282804.b4-ty@bootlin.com \
--to=alexandre.belloni@bootlin.com \
--cc=absicsz@gmail.com \
--cc=devnull@uvos.xyz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=pavel@ucw.cz \
--cc=sebastian.reichel@collabora.com \
--cc=sre@kernel.org \
--cc=tony@atomide.com \
/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).