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: Fri, 11 May 2012 12:04:57 -0600 From: Stephen Warren <swarren@...dotorg.org> To: Joerg Roedel <joerg.roedel@....com> CC: Hiroshi DOYU <hdoyu@...dia.com>, linux-tegra@...r.kernel.org, Grant Likely <grant.likely@...retlab.ca>, Rob Herring <rob.herring@...xeda.com>, Rob Landley <rob@...dley.net>, Ohad Ben-Cohen <ohad@...ery.com>, Tony Lindgren <tony@...mide.com>, Jiri Kosina <jkosina@...e.cz>, Thierry Reding <thierry.reding@...onic-design.de>, devicetree-discuss@...ts.ozlabs.org, linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 1/2] iommu/tegra: smmu: Add device tree support for SMMU On 05/11/2012 03:46 AM, Joerg Roedel wrote: > On Thu, May 10, 2012 at 02:08:33PM -0600, Stephen Warren wrote: >> On 05/10/2012 01:50 AM, Hiroshi DOYU wrote: >>> The necessary info is expected to pass from DT. >>> >>> For more precise resource reservation, there shouldn't be any >>> overlapping of register range between SMMU and MC. SMMU register >>> offset needs to be calculated correctly, based on its register bank. >>> >>> Signed-off-by: Hiroshi DOYU <hdoyu@...dia.com> >> >> Acked-by: Stephen Warren <swarren@...dotorg.org> >> >> I expect patch 1 will go through the IOMMU tree, and I'll take patch 2 >> through the Tegra tree. > > Any reason for splitting it up? The patches touch mostly drivers/iommu. > So to avoid conflicts its probably the best to apply them together. Patch 1 is the driver that touches drivers/iommu and related documentation, whereas patch 2 touches the device tree file in arch/arm/boot/dts. Either of the patches would get conflicts if they were merged into the "other" tree. -- 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