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: <11d12eea-e70f-8bf8-ed1e-f82cf95a20ee@kernel.org>
Date:   Mon, 3 Apr 2023 12:35:45 +0200
From:   Krzysztof Kozlowski <krzk@...nel.org>
To:     Andreas Kemnade <andreas@...nade.info>
Cc:     robh+dt@...nel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, Tony Lindgren <tony@...mide.com>,
        Andrew Davis <afd@...com>
Subject: Re: [PATCH v3 1/2] dt-bindings: omap: Convert omap.txt to yaml

On 03/04/2023 12:18, Andreas Kemnade wrote:
> Hi,
> 
> On Sun, 2 Apr 2023 13:26:46 +0200
> Krzysztof Kozlowski <krzk@...nel.org> wrote:
> 
>> On 01/04/2023 16:02, Andreas Kemnade wrote:
>>> From: Andrew Davis <afd@...com>
>>>
>>> Convert omap.txt to yaml.
>>>
>>> Signed-off-by: Andrew Davis <afd@...com>
>>> [various cleanup, adding Epson Moverio BT-200]
>>> Signed-off-by: Andreas Kemnade <andreas@...nade.info>  
>>
>> Please use scripts/get_maintainers.pl to get a list of necessary people
>> and lists to CC.  It might happen, that command when run on an older
>> kernel, gives you outdated entries.  Therefore please be sure you base
>> your patches on recent Linux kernel.
>>
>> Your CC list is broken in few ways. Just use the script, don't re-invent
>> the addresses.
>>
> well, I am using the script and added a few adresses obviously missing.

And one of them (omap@...nel) was invalid which made it impossible to
reply to you...


> But maybe I have used the script from an older kernel. The patch was against
> linux-next.
> 
> [...]
>>> +      - description: TI DRA7 SoC based platforms
>>> +        items:
>>> +          - enum:
>>> +              - ti,dra718-evm  
>>
>> This is not correct. Maybe you forgot to fix DTS, but anyway it's
>> confusing to have dra718-evm with dra768 SoC. Is this really proper
>> combination?
>>
> dra718-evm has a lot of compatibles, no idea if that is sane.
> And to better discuss such things I added the omap mailinglist (with a typo,
> sorry). To avoid that trouble in the future, I added a patch to MAINTAINERS.
> 
> But I think it is better to not convert dra7 stuff for now, then
> it can be discussed by the right people. 


Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ