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: <164462530187.853991.5366752507698485779.b4-ty@sntech.de>
Date:   Sat, 12 Feb 2022 01:23:36 +0100
From:   Heiko Stuebner <heiko@...ech.de>
To:     Samuel Holland <samuel@...lland.org>
Cc:     Heiko Stuebner <heiko@...ech.de>, Tianling Shen <cnsztl@...il.com>,
        Levin Du <djw@...hip.com.cn>,
        linux-rockchip@...ts.infradead.org, Alex Bee <knaerzche@...il.com>,
        devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        Liang Chen <cl@...k-chips.com>,
        Rob Herring <robh+dt@...nel.org>,
        Chen-Yu Tsai <wenst@...omium.org>,
        linux-kernel@...r.kernel.org, Peter Geis <pgwipeout@...il.com>
Subject: Re: [PATCH 1/3] dt-bindings: arm: rockchip: Add Pine64 PineNote board

On Sat, 29 Jan 2022 23:38:01 -0600, Samuel Holland wrote:
> The PineNote is a tablet from Pine64 based on the RK3566 SoC. There are
> two existing variants of the board. v1.1 was contained in some early
> samples, and v1.2 was sold as the "PineNote Developer Edition".

Applied, thanks!

[1/3] dt-bindings: arm: rockchip: Add Pine64 PineNote board
      commit: a7c9013216f399791ca354cc2e0f4a444837fe39
[2/3] arm64: dts: rockchip: rk356x: Add pdm node
      commit: 79c5f0e52d29a688a951fc818394b529e7e77e3e

-> change ordering for pinctrl properties, as suggested by Michael

[3/3] arm64: dts: rockchip: Add Pine64 PineNote board
      commit: d449121e5e8addcee654250cec298c887ecafb32

-> folded in Johan's review comments
   Though mmc0 can stay at sdhci. I don't think we _need_
   aliases for all, but fixing mmc0 for the internal emmc makes
   a lot of sense.

Best regards,
-- 
Heiko Stuebner <heiko@...ech.de>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ