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: Wed, 20 Oct 2010 11:45:16 +0300 (EEST) From: Hiroshi DOYU <Hiroshi.DOYU@...ia.com> To: felipe.contreras@...il.com Cc: x0095840@...com, felipe.contreras@...ia.com, david.cohen@...ia.com, linux-kernel@...r.kernel.org, linux-omap@...r.kernel.org Subject: Re: [PATCHv4 4/4] iommu: create new api to set valid da range From: "ext felipe.contreras@...il.com" <felipe.contreras@...il.com> Subject: Re: [PATCHv4 4/4] iommu: create new api to set valid da range Date: Wed, 20 Oct 2010 10:35:50 +0200 > On Wed, Oct 20, 2010 at 5:48 AM, Fernando Guzman Lugo <x0095840@...com> wrote: >> Some IOMMUs cannot use the whole 0x0 - 0xFFFFFFFF range. >> With this new API the valid range can be set. >> >> Signed-off-by: Fernando Guzman Lugo <x0095840@...com> > > I don't see the point in having an API. It could be done through > platform data, and the usage of 0xFFFFF000 instead of ULONG_MAX is > independent of this. Using platform data is better, but why dropping da_end? -- 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