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: <20130110191207.GI25591@8bytes.org> Date: Thu, 10 Jan 2013 20:12:08 +0100 From: 'Joerg Roedel' <joro@...tes.org> To: Kukjin Kim <kgene.kim@...sung.com> Cc: 'Cho KyongHo' <pullip.cho@...sung.com>, 'Linux ARM Kernel' <linux-arm-kernel@...ts.infradead.org>, 'Linux IOMMU' <iommu@...ts.linux-foundation.org>, 'Linux Kernel' <linux-kernel@...r.kernel.org>, 'Linux Samsung SOC' <linux-samsung-soc@...r.kernel.org>, 'Hyunwoong Kim' <khw0178.kim@...sung.com>, 'Prathyush' <prathyush.k@...sung.com>, 'Rahul Sharma' <rahul.sharma@...sung.com>, 'Subash Patel' <supash.ramaswamy@...aro.org> Subject: Re: [PATCH v6 00/12] iommu/exynos: Fixes and Enhancements of System MMU driver with DT On Thu, Jan 10, 2013 at 10:34:48AM -0800, Kukjin Kim wrote: > Hmm, I think, just one [7/12] patch does matter so if you could create topic > branch and apply [7/12] patch firstly before other drivers/ changes would be > better to me. It's OK on both trees if I just _merge_ the first [7/12] > commit in the topic branch you provided for exynos-iommu. But you know, you > don't have to rebase it once I merge it in Samsung tree. > > How about? Sounds good. Should I take the patch directly from this post? I would add your Acked-by then and make it the base for the arm/exynos branch. Once the branch is set-up, as usual it will not be rebased. Joerg -- 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