linux-kernel - Re: [PATCH v2 00/10] soc: sunxi: sram: Fixes and D1 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <de99e42e-e721-834a-e532-ace515f70ba7@microchip.com>
Date:   Mon, 15 Aug 2022 06:59:47 +0000
From:   <Conor.Dooley@...rochip.com>
To:     <samuel@...lland.org>, <wens@...e.org>, <jernej.skrabec@...il.com>
CC:     <arnd@...db.de>, <hdegoede@...hat.com>, <icenowy@...c.io>,
        <krzysztof.kozlowski+dt@...aro.org>, <mripard@...nel.org>,
        <robh+dt@...nel.org>, <devicetree@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>, <linux-sunxi@...ts.linux.dev>
Subject: Re: [PATCH v2 00/10] soc: sunxi: sram: Fixes and D1 support

On 15/08/2022 07:57, Conor Dooley wrote:
> Hey Samuel,
> On 15/08/2022 05:12, Samuel Holland wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>
>> This series cleans up a few issues in the system controller driver, and
>> then expands the exported regmap to support one of the pairs of LDOs
>> built in to the D1 SoC.
>>
>> Eventually, we will need to update the SRAM region claiming API so
>> ownership can be swapped back and forth by consumer drivers. This will
>> be necessary for uploading firmware to the R329/D1 DSPs, but it is not
>> needed for initial bringup.
> 
> I tried this series on top of both 6.0-rc1 & next, but I saw a shed
> load of errors from dtbs_check. I'll take a look at the rest of the
> series later on, but just FYI. I know I have seen patches going into
> different subsystems so I assume you're working on it. However, it
> would be nice to let us what all the dependencies for this series are
> dt-binding wise in the cover letter.
> I have been trying to get riscv down to 0 warnings and would not be
> in favour of accepting patches that go in the other direction.
> (This patchset currently produces about 75 warnings)
> 

Ignore this, I read the wrong cover letter. Sorry.