diff for duplicates of <11003810.ccjcAXkzhi@phil> diff --git a/a/1.txt b/N1/1.txt index c6d1f23..0a29f75 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -4,11 +4,11 @@ Am Dienstag, 10. Mai 2016, 16:50:46 schrieb John Keeping: > 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 3cace38..cd84d0e 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,14 +1,8 @@ "ref\020160510155046.24515-1-john@metanate.com\0" - "ref\020160510155046.24515-1-john-HooS5bfzL4hWk0Htik3J/w@public.gmane.org\0" - "From\0Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>\0" - "Subject\0Re: [PATCH] iommu/rockchip: fix zap cache during device attach\0" + "From\0heiko@sntech.de (Heiko Stuebner)\0" + "Subject\0[PATCH] iommu/rockchip: fix zap cache during device attach\0" "Date\0Sat, 14 May 2016 22:19:43 +0200\0" - "To\0John Keeping <john-HooS5bfzL4hWk0Htik3J/w@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" "Am Dienstag, 10. Mai 2016, 16:50:46 schrieb John Keeping:\n" @@ -17,11 +11,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" @@ -29,4 +23,4 @@ "\n" Heiko -163c04d2bee667e76d7f8ed211a475fa47959a564e1b661eddf08ef97f5da4fb +fbb80187b44d2eadf01f50fad77639b0ab7e7d88ff073783ffbd5b7caf053704
diff --git a/a/1.txt b/N2/1.txt index c6d1f23..0a29f75 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -4,11 +4,11 @@ Am Dienstag, 10. Mai 2016, 16:50:46 schrieb John Keeping: > 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 3cace38..7d39293 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,14 +1,14 @@ "ref\020160510155046.24515-1-john@metanate.com\0" - "ref\020160510155046.24515-1-john-HooS5bfzL4hWk0Htik3J/w@public.gmane.org\0" - "From\0Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>\0" + "From\0Heiko Stuebner <heiko@sntech.de>\0" "Subject\0Re: [PATCH] iommu/rockchip: fix zap cache during device attach\0" "Date\0Sat, 14 May 2016 22:19:43 +0200\0" - "To\0John Keeping <john-HooS5bfzL4hWk0Htik3J/w@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\0John Keeping <john@metanate.com>\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" "Am Dienstag, 10. Mai 2016, 16:50:46 schrieb John Keeping:\n" @@ -17,11 +17,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" @@ -29,4 +29,4 @@ "\n" Heiko -163c04d2bee667e76d7f8ed211a475fa47959a564e1b661eddf08ef97f5da4fb +3af1142525fb4204ef73e92e13c5a8042c67864835c223fd3536d91fa5431d10
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.