| 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
| ||
|
Message-ID: <55FC49B8.3020100@arm.com> Date: Fri, 18 Sep 2015 18:28:24 +0100 From: Andre Przywara <andre.przywara@....com> To: David Miller <davem@...emloft.net> Cc: "joro@...tes.org" <joro@...tes.org>, "sparclinux@...r.kernel.org" <sparclinux@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org> Subject: Re: [PATCH] iommu-common: only compile lib/iommu_common.c for Sparc64 Hi David, On 18/09/15 18:09, David Miller wrote: > From: Andre Przywara <andre.przywara@....com> > Date: Fri, 18 Sep 2015 10:03:40 +0100 > >> Or do you know of a simpler way to fixing it properly which could make >> it still into 4.3? > > All I worry about is that if you take it out of the build, doing > the proper fix will suddenly become very low priority and be > forgotten about completely. > > Whereas if it actually blocks the build for someone, it's a high > priority issue to address. I see. What about if I provide the two patches at the same time? An easy fix for 4.3 and the proper fix for 4.4? You can then even choose to take the proper fix for 4.3 if it's reasonably low risk. I will try sending something on Monday. Cheers, Andre. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists