linux-kernel - Re: [PATCH 00/16] IOMMU driver for Kirin 960/970

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: <20200817082106.GA16296@infradead.org>
Date:   Mon, 17 Aug 2020 09:21:06 +0100
From:   Christoph Hellwig <hch@...radead.org>
To:     Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linuxarm@...wei.com, mauro.chehab@...wei.com,
        John Stultz <john.stultz@...aro.org>,
        Manivannan Sadhasivam <mani@...nel.org>,
        Rob Herring <robh+dt@...nel.org>,
        linux-arm-kernel@...ts.infradead.org,
        Wei Xu <xuwei5@...ilicon.com>, devicetree@...r.kernel.org,
        Joerg Roedel <joro@...tes.org>, Joerg Roedel <jroedel@...e.de>,
        iommu@...ts.linux-foundation.org,
        Chenfeng <puck.chen@...ilicon.com>, devel@...verdev.osuosl.org,
        Suzhuangluan <suzhuangluan@...ilicon.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/16] IOMMU driver for Kirin 960/970

On Mon, Aug 17, 2020 at 09:49:59AM +0200, Mauro Carvalho Chehab wrote:
> Add a driver for the Kirin 960/970 iommu.
> 
> As on the past series, this starts from the original 4.9 driver from
> the 96boards tree:
> 
> 	https://github.com/96boards-hikey/linux/tree/hikey970-v4.9
> 
> The remaining patches add SPDX headers and make it build and run with
> the upstream Kernel.

Please don't add iommu drivers to staging, and just work with the
maintainers to properly clean it up.

I also don't think adding a totally out of date not compiling version
is a good idea.  Please do a proper rollup, and if required (probably
not in this case), split it into useful chunks.