linux-kernel - Re: [PATCH v2 4/5] memory: brcmstb_dpfe: introduce version-specific compatible strings

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

Date: Thu, 1 Feb 2024 14:40:35 -0800
From: Markus Mayer <mmayer@...adcom.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: Florian Fainelli <florian.fainelli@...adcom.com>, Rob Herring <robh+dt@...nel.org>, 
	Conor Dooley <conor+dt@...nel.org>, 
	Linux ARM Kernel List <linux-arm-kernel@...ts.infradead.org>, 
	Device Tree Mailing List <devicetree@...r.kernel.org>, Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 4/5] memory: brcmstb_dpfe: introduce version-specific
 compatible strings

On Tue, 23 Jan 2024 at 13:28, Krzysztof Kozlowski
<krzysztof.kozlowski@...aro.org> wrote:
>
> On 19/01/2024 22:52, Markus Mayer wrote:
> > Introduce compatible strings brcm,dpfe-cpu-v1 through brcm,dpfe-cpu-v3
> > to the Broadcom DPFE driver.
>
> Nothing improved here. I think my last comment was pretty clear what I
> expect.

You are correct. Nothing changed here. I did not get the impression
that you were asking for changes to the actual driver code.

As I said in my response to the previous patch, I am trying my best to
work with maintainers and other community members providing feedback.

Please explain in further detail what you are looking for. Maybe this
will already happen in conjunction with patch 3/5. Your responses
there may already answer my question here. I guess we'll find out.

Regards,
-Markus

> Best regards,
> Krzysztof