[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <159372105822.57284.8366488507603282804.b4-ty@bootlin.com>
Date: Thu, 2 Jul 2020 22:23:10 +0200
From: Alexandre Belloni <alexandre.belloni@...tlin.com>
To: Dev Null <devnull@...s.xyz>,
Sebastian Reichel <sebastian.reichel@...labora.com>,
Sebastian Reichel <sre@...nel.org>
Cc: Alexandre Belloni <alexandre.belloni@...tlin.com>,
linux-omap@...r.kernel.org, Pavel Machek <pavel@....cz>,
linux-kernel@...r.kernel.org, Merlijn Wajer <merlijn@...zup.org>,
Tony Lindgren <tony@...mide.com>, linux-rtc@...r.kernel.org,
"Sicelo A . Mhlongo" <absicsz@...il.com>
Subject: Re: [PATCH] rtc: cpcap: fix range
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@...tlin.com>
Powered by blists - more mailing lists