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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <163698368315.132512.16798807565852524443.b4-ty@canonical.com>
Date:   Mon, 15 Nov 2021 14:41:25 +0100
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
To:     linux-arm-kernel@...ts.infradead.org,
        Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>,
        linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:     David Virag <virag.david003@...il.com>
Subject: Re: [PATCH] soc: samsung: exynos-chipid: describe which SoCs go with compatibles

On Sun, 31 Oct 2021 21:52:12 +0100, Krzysztof Kozlowski wrote:
> The Exynos ChipID driver, like most of the Exynos drivers, uses one
> compatible for entire family of compatible devices using one devicetree
> "compatible".  The compatibility is here described by programming
> interface (register layout), not by actual values, so the product ID
> register on one family of devices has different values for different
> SoCs.
> 
> [...]

Applied, thanks!

[1/1] soc: samsung: exynos-chipid: describe which SoCs go with compatibles
      commit: 569e45a1135497d8dddc647bc615e26c49b070a8

Best regards,
-- 
Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ