linux-kernel - Re: [PATCH 4/4] iommu: make inclusion of riscv directory conditional

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: <Z9vOqabp0GwimC1J@8bytes.org>
Date: Thu, 20 Mar 2025 09:15:37 +0100
From: Joerg Roedel <joro@...tes.org>
To: Rolf Eike Beer <eb@...ix.com>
Cc: Will Deacon <will@...nel.org>, iommu@...ts.linux.dev,
	linux-kernel@...r.kernel.org,
	Tomasz Jeznach <tjeznach@...osinc.com>,
	Nick Kossifidis <mick@....forth.gr>,
	Sebastien Boeuf <seb@...osinc.com>,
	Lu Baolu <baolu.lu@...ux.intel.com>,
	Palmer Dabbelt <palmer@...osinc.com>,
	Paul Walmsley <paul.walmsley@...ive.com>,
	Albert Ou <aou@...s.berkeley.edu>, Alexandre Ghiti <alex@...ti.fr>
Subject: Re: [PATCH 4/4] iommu: make inclusion of riscv directory conditional

On Thu, Mar 20, 2025 at 09:10:34AM +0100, Rolf Eike Beer wrote:
> Yes, and I can send those cleanups as a followup if you like. But for the first 
> step I wanted to keep this as less invasive as it could be. And to be honest I 
> didn't want to invest time to do this cleanups if it's unclear if they would 
> be rejected anyway because these things are this way on purpose.

I am fine with these cleanups and they are contained enough to also take
care of the vendor-specific Makefiles in the same series.

Regards,

	Joerg