linux-kernel - Re: [PATCH v3 0/2] add reset-source RTC binding, update pcf2127 driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <160833946513.3453721.3470869578503319105.b4-ty@bootlin.com>
Date:   Sat, 19 Dec 2020 01:58:06 +0100
From:   Alexandre Belloni <alexandre.belloni@...tlin.com>
To:     linux-rtc@...r.kernel.org,
        Rasmus Villemoes <rasmus.villemoes@...vas.dk>
Cc:     Alexandre Belloni <alexandre.belloni@...tlin.com>,
        Qiang Zhao <qiang.zhao@....com>, linux-kernel@...r.kernel.org,
        Uwe Kleine-König 
        <u.kleine-koenig@...gutronix.de>,
        Bruno Thomsen <bruno.thomsen@...il.com>,
        Rob Herring <robh+dt@...nel.org>, devicetree@...r.kernel.org
Subject: Re: [PATCH v3 0/2] add reset-source RTC binding, update pcf2127 driver

On Fri, 18 Dec 2020 11:10:52 +0100, Rasmus Villemoes wrote:
> This adds a reset-source RTC DT binding, as suggested by Alexandre,
> and resends Uwe's patch making use of that property in pcf2127 driver
> to avoid the driver exposing a watchdog that doesn't work (and
> potentially shuffling the enumeration of the existing devices that do
> work).
> 
> v3: elide the refactoring patch already in -next (5d78533a0c53 - rtc:
> pcf2127: move watchdog initialisation to a separate function), make
> sure to cc the DT binding list.
> 
> [...]

Applied, thanks!

[1/2] dt-bindings: rtc: add reset-source property
      commit: 320d159e2d63a97a40f24cd6dfda5a57eec65b91
[2/2] rtc: pcf2127: only use watchdog when explicitly available
      commit: 71ac13457d9d1007effde65b54818106b2c2b525

Best regards,
-- 
Alexandre Belloni <alexandre.belloni@...tlin.com>