[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAODwPW-KS4f8GQ2ooOhdA+ZrDUPvvv6r0795f+QyHrjWagMHhA@mail.gmail.com>
Date: Thu, 3 Dec 2015 08:53:22 -0800
From: Julius Werner <jwerner@...omium.org>
To: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
Cc: Julius Werner <jwerner@...omium.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Alessandro Zummo <a.zummo@...ertech.it>,
Doug Anderson <dianders@...omium.org>,
Sonny Rao <sonnyrao@...omium.org>,
Chris Zhong <zyw@...k-chips.com>,
Heiko Stuebner <heiko@...ech.de>,
LKML <linux-kernel@...r.kernel.org>, rtc-linux@...glegroups.com
Subject: Re: [rtc-linux] [PATCH] RTC: RK808: Work around hardware bug on
November 31st
> I would have liked to be in copy of that mail. Maybe you used
> get_maintainers on an old tree?
Oops, yes, sorry, I ran it on a 3.14 backport and then just added
people I found in older patches for that file.
> I hope reading the time properly fails thanks to the rtc_valid_tm(tm) in
> __rtc_read_time().
It should, yeah. I haven't tested it (beyond compiling) on master, and
our version doesn't have that code yet, so I can't say for sure.
> It will also happen if nobody reads the RTC time for that day (highly
> improbable in a default configuration). Do you need that patch for 4.4
> or can it wait 4.5?
True. I don't really need the patch to land in a particular release
since we maintain our own tree with backports. It would probably still
be nice if you can get it into the 4.4 LTS to reduce the chance this
will hit anyone again next year.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists