diff for duplicates of <20180624140210.03416dea@bbrezillon> diff --git a/a/1.txt b/N1/1.txt index 6f7be05..5b0e788 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -134,7 +134,3 @@ envision what I3C muxes (if they ever exist) will look like? How about applying this approach to I2C first and see how it flies. Changing the I3C framework afterwards (when I3C muxes come in) shouldn't be that complicated. --- -To unsubscribe from this list: send the line "unsubscribe linux-doc" in -the body of a message to majordomo@vger.kernel.org -More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index 66e100b..3822852 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -27,17 +27,7 @@ Rob Herring <robh+dt@kernel.org> Pawel Moll <pawel.moll@arm.com> Mark Rutland <mark.rutland@arm.com> - Ian Campbell <ijc+devicetree@hellion.org.uk> - Kumar Gala <galak@codeaurora.org> - devicetree@vger.kernel.org - linux-kernel@vger.kernel.org - Vitor Soares <Vitor.Soares@synopsys.com> - Geert Uytterhoeven <geert@linux-m68k.org> - Linus Walleij <linus.walleij@linaro.org> - Xiang Lin <Xiang.Lin@synaptics.com> - linux-gpio@vger.kernel.org - Sekhar Nori <nsekhar@ti.com> - " Przemyslaw Gaj <pgaj@cadence.com>\0" + " Ian Campbell <ijc+devicetree@hellion>\0" "\00:1\0" "b\0" "On Sat, 23 Jun 2018 23:40:36 +0200\n" @@ -175,10 +165,6 @@ "\n" "How about applying this approach to I2C first and see how it flies.\n" "Changing the I3C framework afterwards (when I3C muxes come in)\n" - "shouldn't be that complicated.\n" - "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-doc\" in\n" - "the body of a message to majordomo@vger.kernel.org\n" - More majordomo info at http://vger.kernel.org/majordomo-info.html + shouldn't be that complicated. -0448eca5ea464329dfe0222d81f14d3e31333550bd009b8d189998b7643bc900 +a099bb63c171ecf756b4c12a51ae740a76ccd6173201b92650c79feae46f5ff9
diff --git a/a/1.txt b/N2/1.txt index 6f7be05..5b0e788 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -134,7 +134,3 @@ envision what I3C muxes (if they ever exist) will look like? How about applying this approach to I2C first and see how it flies. Changing the I3C framework afterwards (when I3C muxes come in) shouldn't be that complicated. --- -To unsubscribe from this list: send the line "unsubscribe linux-doc" in -the body of a message to majordomo@vger.kernel.org -More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N2/content_digest index 66e100b..2546655 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -175,10 +175,6 @@ "\n" "How about applying this approach to I2C first and see how it flies.\n" "Changing the I3C framework afterwards (when I3C muxes come in)\n" - "shouldn't be that complicated.\n" - "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-doc\" in\n" - "the body of a message to majordomo@vger.kernel.org\n" - More majordomo info at http://vger.kernel.org/majordomo-info.html + shouldn't be that complicated. -0448eca5ea464329dfe0222d81f14d3e31333550bd009b8d189998b7643bc900 +597e9209de4ad92605485512515defae0ce7606f96bbda73995205be4bd60ee7
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.