linux-kernel - Re: [PATCH v2 1/2] dt-bindings: rtc: ds1307: Add support for Epson RX8111

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <c313e8ba-e44a-66aa-3577-31b5df728e90@topic.nl>
Date:   Fri, 4 Nov 2022 07:20:10 +0100
From:   Mike Looijmans <mike.looijmans@...ic.nl>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        Alexandre Belloni <alexandre.belloni@...tlin.com>,
        glazveze@...ta.nl
CC:     linux-rtc@...r.kernel.org, Alessandro Zummo <a.zummo@...ertech.it>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Rob Herring <robh+dt@...nel.org>, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: rtc: ds1307: Add support for Epson
 RX8111


Met vriendelijke groet / kind regards,

Mike Looijmans
System Expert


TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands

T: +31 (0) 499 33 69 69
E: mike.looijmans@...icproducts.com
W: www.topic.nl

Please consider the environment before printing this e-mail
On 04-11-2022 02:50, Krzysztof Kozlowski wrote:
> On 03/11/2022 18:43, Alexandre Belloni wrote:
>> On 01/11/2022 09:31:21+0100, glazveze@...ta.nl wrote:
>>> From: Mike Looijmans <mike.looijmans@...ic.nl>
>>>
>>> The rx_8111 is quite similar to the rx_8030. This adds support for this
>>> chip to the ds1307 driver.
>>>
>>> This adds the entry to the devicetree bindings.
>>>
>>> Signed-off-by: Mike Looijmans <mike.looijmans@...ic.nl>
>>
>> The SoB has to match the sender address, it took some time to me to
>> understand this was for the same person...
> 
> Ugh, so who sent it?
> 

I did, but our company mail server is incapable of sending patches (it will 
have mangled this mail as well), so I sent it from a different provider.