diff for duplicates of <20160515111638.GA9715@river> diff --git a/a/1.txt b/N1/1.txt index 5c170f3..9cd0559 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -5,11 +5,11 @@ On Sat, May 14, 2016 at 10:19:43PM +0200, Heiko Stuebner wrote: > > and talking to MMUs that we shouldn't be. > > > > Fixes: cd6438c5f844 ("iommu/rockchip: Reconstruct to support multi -> > slaves") Signed-off-by: John Keeping <john-HooS5bfzL4hWk0Htik3J/w@public.gmane.org> +> > slaves") Signed-off-by: John Keeping <john@metanate.com> > > on a rk3288-veyron -> Tested-by: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org> -> Reviewed-by: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org> +> Tested-by: Heiko Stuebner <heiko@sntech.de> +> Reviewed-by: Heiko Stuebner <heiko@sntech.de> > > I was wondering for a short time why this didn't spew warnings until I > realized that the iommu->bases[i] is of course a void* . diff --git a/a/content_digest b/N1/content_digest index 1d8589b..ac7c501 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,14 +1,9 @@ "ref\020160510155046.24515-1-john@metanate.com\0" "ref\011003810.ccjcAXkzhi@phil\0" - "From\0John Keeping <john-HooS5bfzL4hWk0Htik3J/w@public.gmane.org>\0" - "Subject\0Re: [PATCH] iommu/rockchip: fix zap cache during device attach\0" + "From\0john@metanate.com (John Keeping)\0" + "Subject\0[PATCH] iommu/rockchip: fix zap cache during device attach\0" "Date\0Sun, 15 May 2016 12:16:39 +0100\0" - "To\0Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>\0" - "Cc\0linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" - linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org - iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org - ZhengShunQian <zhengsq-TNX95d0MmH7DzftRWevZcw@public.gmane.org> - " linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On Sat, May 14, 2016 at 10:19:43PM +0200, Heiko Stuebner wrote:\n" @@ -18,11 +13,11 @@ "> > and talking to MMUs that we shouldn't be.\n" "> > \n" "> > Fixes: cd6438c5f844 (\"iommu/rockchip: Reconstruct to support multi\n" - "> > slaves\") Signed-off-by: John Keeping <john-HooS5bfzL4hWk0Htik3J/w@public.gmane.org>\n" + "> > slaves\") Signed-off-by: John Keeping <john@metanate.com>\n" "> \n" "> on a rk3288-veyron\n" - "> Tested-by: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>\n" - "> Reviewed-by: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>\n" + "> Tested-by: Heiko Stuebner <heiko@sntech.de>\n" + "> Reviewed-by: Heiko Stuebner <heiko@sntech.de>\n" "> \n" "> I was wondering for a short time why this didn't spew warnings until I \n" "> realized that the iommu->bases[i] is of course a void* .\n" @@ -30,4 +25,4 @@ "Yes, although sparse catches it because iommu->bases[i] is __iomem so it\n" shows up as a namespace warning. -40998a664992dbeef7edc7eff12582cb0f5999fd51c50a9609a73cc5cb9fdbbe +72fa05b5fdc139e6b133735ab608c1fec2b2deed9b1b3d606b9b2a7a85d249c8
diff --git a/a/1.txt b/N2/1.txt index 5c170f3..9cd0559 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -5,11 +5,11 @@ On Sat, May 14, 2016 at 10:19:43PM +0200, Heiko Stuebner wrote: > > and talking to MMUs that we shouldn't be. > > > > Fixes: cd6438c5f844 ("iommu/rockchip: Reconstruct to support multi -> > slaves") Signed-off-by: John Keeping <john-HooS5bfzL4hWk0Htik3J/w@public.gmane.org> +> > slaves") Signed-off-by: John Keeping <john@metanate.com> > > on a rk3288-veyron -> Tested-by: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org> -> Reviewed-by: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org> +> Tested-by: Heiko Stuebner <heiko@sntech.de> +> Reviewed-by: Heiko Stuebner <heiko@sntech.de> > > I was wondering for a short time why this didn't spew warnings until I > realized that the iommu->bases[i] is of course a void* . diff --git a/a/content_digest b/N2/content_digest index 1d8589b..37ee773 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,14 +1,15 @@ "ref\020160510155046.24515-1-john@metanate.com\0" "ref\011003810.ccjcAXkzhi@phil\0" - "From\0John Keeping <john-HooS5bfzL4hWk0Htik3J/w@public.gmane.org>\0" + "From\0John Keeping <john@metanate.com>\0" "Subject\0Re: [PATCH] iommu/rockchip: fix zap cache during device attach\0" "Date\0Sun, 15 May 2016 12:16:39 +0100\0" - "To\0Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>\0" - "Cc\0linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" - linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org - iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org - ZhengShunQian <zhengsq-TNX95d0MmH7DzftRWevZcw@public.gmane.org> - " linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org\0" + "To\0Heiko Stuebner <heiko@sntech.de>\0" + "Cc\0iommu@lists.linux-foundation.org" + Joerg Roedel <joro@8bytes.org> + linux-arm-kernel@lists.infradead.org + linux-rockchip@lists.infradead.org + linux-kernel@vger.kernel.org + " ZhengShunQian <zhengsq@rock-chips.com>\0" "\00:1\0" "b\0" "On Sat, May 14, 2016 at 10:19:43PM +0200, Heiko Stuebner wrote:\n" @@ -18,11 +19,11 @@ "> > and talking to MMUs that we shouldn't be.\n" "> > \n" "> > Fixes: cd6438c5f844 (\"iommu/rockchip: Reconstruct to support multi\n" - "> > slaves\") Signed-off-by: John Keeping <john-HooS5bfzL4hWk0Htik3J/w@public.gmane.org>\n" + "> > slaves\") Signed-off-by: John Keeping <john@metanate.com>\n" "> \n" "> on a rk3288-veyron\n" - "> Tested-by: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>\n" - "> Reviewed-by: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>\n" + "> Tested-by: Heiko Stuebner <heiko@sntech.de>\n" + "> Reviewed-by: Heiko Stuebner <heiko@sntech.de>\n" "> \n" "> I was wondering for a short time why this didn't spew warnings until I \n" "> realized that the iommu->bases[i] is of course a void* .\n" @@ -30,4 +31,4 @@ "Yes, although sparse catches it because iommu->bases[i] is __iomem so it\n" shows up as a namespace warning. -40998a664992dbeef7edc7eff12582cb0f5999fd51c50a9609a73cc5cb9fdbbe +a86a4808f5637bda026cf738868286cb4be15e8c171e5618e8757806a1af52db
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.