| 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
| ||
|
Date: Mon, 3 Nov 2014 10:57:16 +0000 From: Will Deacon <will.deacon@....com> To: Stefano Stabellini <stefano.stabellini@...citrix.com> Cc: "xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>, "konrad.wilk@...cle.com" <konrad.wilk@...cle.com>, "Ian.Campbell@...rix.com" <Ian.Campbell@...rix.com>, "david.vrabel@...rix.com" <david.vrabel@...rix.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, Catalin Marinas <Catalin.Marinas@....com> Subject: Re: [PATCH v7 3/8] arm64: introduce is_device_dma_coherent On Mon, Nov 03, 2014 at 10:46:03AM +0000, Stefano Stabellini wrote: > On Mon, 27 Oct 2014, Stefano Stabellini wrote: > > Introduce a boolean flag and an accessor function to check whether a > > device is dma_coherent. Set the flag from set_arch_dma_coherent_ops. > > > > Signed-off-by: Stefano Stabellini <stefano.stabellini@...citrix.com> > > Signed-off-by: Catalin Marinas <catalin.marinas@....com> > > CC: will.deacon@....com > > Will, Catalin, > are you OK with this patch? It would be nicer if the dma_coherent flag didn't have to be duplicated by each architecture in dev_archdata. Is there any reason not to put it in the core code? Will -- 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