linux-kernel - Re: [PATCH 0/5] clk: Add Baikal-T1 SoC Clock Control Unit support

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: <158380581761.149997.14282326995500288620@swboyd.mtv.corp.google.com>
Date:   Mon, 09 Mar 2020 19:03:37 -0700
From:   Stephen Boyd <sboyd@...nel.org>
To:     Alexey Malahov <Alexey.Malahov@...kalelectronics.ru>,
        Ekaterina Skachko <Ekaterina.Skachko@...kalelectronics.ru>,
        Mark Rutland <mark.rutland@....com>,
        Maxim Kaurkin <Maxim.Kaurkin@...kalelectronics.ru>,
        Michael Turquette <mturquette@...libre.com>,
        Paul Burton <paulburton@...nel.org>,
        Pavel Parkhomenko <Pavel.Parkhomenko@...kalelectronics.ru>,
        Ralf Baechle <ralf@...ux-mips.org>,
        Ramil Zaripov <Ramil.Zaripov@...kalelectronics.ru>,
        Rob Herring <robh+dt@...nel.org>,
        Sergey Semin <Sergey.Semin@...kalelectronics.ru>,
        Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
        Vadim Vlasov <V.Vlasov@...kalelectronics.ru>,
        devicetree@...r.kernel.org, linux-clk@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] clk: Add Baikal-T1 SoC Clock Control Unit support

Quoting Sergey Semin (2020-03-09 17:21:26)
> 
> It appears our corporate email server changes the Message-Id field of 
> messages passing through it. Due to that the emails threading gets to be
> broken. I'll resubmit the properly structured patchset as soon as our system
> administrator fixes the problem. Sorry for the inconvenience caused by it.
> 

Please trim replies. I had to scroll and that made my life super hard! :P 

Anyway, I see a thread so maybe my MUA figured it out. I can wait for it
to be sorted on the corporate end though.