linux-kernel - Re: [PATCH v2 0/4] Add 8qm SMMU information

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]

Date: Fri, 2 Feb 2024 11:05:11 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Frank Li <Frank.Li@....com>
Cc: Ulf Hansson <ulf.hansson@...aro.org>, Rob Herring <robh+dt@...nel.org>,
 Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, Conor Dooley
 <conor+dt@...nel.org>, Shawn Guo <shawnguo@...nel.org>, Sascha Hauer
 <s.hauer@...gutronix.de>, Pengutronix Kernel Team <kernel@...gutronix.de>,
 Fabio Estevam <festevam@...il.com>, NXP Linux Team <linux-imx@....com>, Wei
 Fang <wei.fang@....com>, Shenwei Wang <shenwei.wang@....com>, Clark Wang
 <xiaoning.wang@....com>, "David S. Miller" <davem@...emloft.net>, Eric
 Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
 linux-mmc@...r.kernel.org, devicetree@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
 netdev@...r.kernel.org, imx@...ts.linux.dev
Subject: Re: [PATCH v2 0/4] Add 8qm SMMU information

On Thu, 01 Feb 2024 15:22:40 -0500 Frank Li wrote:
>       dt-bindings: mmc: fsl-imx-esdhc: add iommus property
>       dt-bindings: net: fec: add iommus property
>       arm64: dts: imx8qm: add smmu node
>       arm64: dts: imx8qm: add smmu stream id information
> 
>  .../devicetree/bindings/mmc/fsl-imx-esdhc.yaml     |  3 ++
>  Documentation/devicetree/bindings/net/fsl,fec.yaml |  3 ++
>  arch/arm64/boot/dts/freescale/imx8qm-ss-conn.dtsi  |  6 ++++
>  arch/arm64/boot/dts/freescale/imx8qm.dtsi          | 41 ++++++++++++++++++++++

Any preference on whether all these go via a platform tree,
or should we pick up the net patch to netdev? I guess taking
the DTB via netdev would be the usual way to handle this?