linux-kernel - Re: [PATCH 0/4] Fix vendor strings on Rockchip boards

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: <cd648b49-b954-45e5-aba7-dee85c0785e5@feathertop.org>
Date: Thu, 15 Feb 2024 11:28:33 +1100
From: Tim Lunn <tim@...thertop.org>
To: Conor Dooley <conor@...nel.org>
Cc: Dragan Simic <dsimic@...jaro.org>, linux-rockchip@...ts.infradead.org,
 Andy Yan <andyshrk@....com>,
 AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
 Chris Morgan <macromorgan@...mail.com>, Conor Dooley <conor+dt@...nel.org>,
 Cristian Ciocaltea <cristian.ciocaltea@...labora.com>,
 David Heidelberg <david@...t.cz>, Heiko Stuebner <heiko@...ech.de>,
 Jagan Teki <jagan@...eble.ai>,
 Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
 Ondrej Jirman <megi@....cz>, Rob Herring <robh+dt@...nel.org>,
 Tianling Shen <cnsztl@...il.com>, devicetree@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] Fix vendor strings on Rockchip boards

Hi Conor,

On 2/15/24 05:12, Conor Dooley wrote:
> On Wed, Feb 14, 2024 at 03:27:08PM +1100, Tim Lunn wrote:
>> Hi Dragan,
>>
>> On 2/14/24 15:14, Dragan Simic wrote:
>>> Hello Tim,
>>>
>>> On 2024-02-14 05:07, Tim Lunn wrote:
>>>> A couple of rockchip boards incorrectly list their vendor as Rockchip
>>>> when they are in fact not manufactured by Rockchip.
>>>>
>>>> Fix the vendor strings to correctly list the manufacturer
>>> Just checking, have you verified that the old, incorrect "compatible"
>>> strings from the board dts files aren't used anywhere in the kernel code,
>>> such as in some drivers?
>>>
>> Yes I checked that, there are no remaining references to the old/incorrect
>> compatible strings in kernel code
> What about other code? Like a BSD or a bootloader? If nothing is using
> them
> Acked-by: Conor Dooley <conor.dooley@...rochip.com>
>
> Fixes tags I think wouldn't go amiss, but I'm not expecting a resend
> with them.
I've added the fixes tags to the email thread.

Regards
   Tim
>
> Cheers,
> Conor.