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: <17c3ee70-66e3-418f-8c79-926c8a139d16@kernel.org>
Date: Wed, 5 Nov 2025 10:06:02 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Songwei Chai <songwei.chai@....qualcomm.com>
Cc: andersson@...nel.org, alexander.shishkin@...ux.intel.com,
 kernel@....qualcomm.com, mike.leach@...aro.org, suzuki.poulose@....com,
 linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 linux-arm-msm@...r.kernel.org, coresight@...ts.linaro.org,
 devicetree@...r.kernel.org
Subject: Re: [PATCH v7 1/7] dt-bindings: arm: Add support for Qualcomm TGU
 trace

On 05/11/2025 09:49, Songwei Chai wrote:

> Once again, I apologize for not including these modifications in the 
> changelog.
> 
>> All qcom coresight bindings are called coresight and I do not see reason
>> why this is being changed.
> 
> The reason for removing the |coresight| keywords is that this patch 
> series was not
> 
> accepted by the maintainers of the Coresight subsystem (as explained in 
> the cover letter).
> 
> Therefore, we decided to make it a Qualcomm-specific driver.

Use standard email paragraphs

not

broken

by

two lines each.

Anyway, above discussion explains nothing about compatible. I might be
missing something, so please quote here Mike the part where he asks to
*change the compatible and hardware name*. Please quote EXACTLY that part.

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ