All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <55EF8C65.4030706@kernel.org>

diff --git a/a/content_digest b/N1/content_digest
index 13b1756..0ae08a4 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -22,7 +22,33 @@
   Felipe Balbi <balbi@ti.com>
   Linux PWM List <linux-pwm@vger.kernel.org>
  " Terje Bergstr\303\266m <tbergstrom@nvidia.com>"
- " Greg Kroah-Hartman <gregkh@linuxfoundation.org>\0"
+  Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+  Jingoo Han <jingoohan1@gmail.com>
+  David Airlie <airlied@linux.ie>
+  Michael Turquette <mturquette@baylibre.com>
+  linux-clk@vger.kernel.org
+  dmaengine@vger.kernel.org
+  Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>
+  Tomi Valkeinen <tomi.valkeinen@ti.com>
+  Grant Likely <grant.likely@linaro.org>
+  Sebastian Reichel <sre@kernel.org>
+  Frank Rowand <frowand.list@gmail.com>
+  Alexandre Courbot <gnurou@gmail.com>
+  linux-pm@vger.kernel.org <linux-pm@vger.kernel.org>
+  Stephen Boyd <sboyd@codeaurora.org>
+  Wolfram Sang <wsa@the-dreams.de>
+  Russell King <linux@arm.linux.org.uk>
+  linux-gpio@vger.kernel.org <linux-gpio@vger.kernel.org>
+  Vinod Koul <vinod.koul@intel.com>
+  Liam Girdwood <lgirdwood@gmail.com>
+  dri-devel <dri-devel@lists.freedesktop.org>
+  Lee Jones <lee.jones@linaro.org>
+  linux-tegra@vger.kernel.org <linux-tegra@vger.kernel.org>
+  Dan Williams <dan.j.williams@intel.com>
+  Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
+  David Woodhouse <dwmw2@infradead.org>
+  Kishon Vijay Abraham I <kishon@ti.com>
+ " linux-i2c@vger.kernel.org <linux-i2c@vger.kernel.org>\0"
  "\00:1\0"
  "b\0"
  "On 09/08/2015 02:30 AM, Tomeu Vizoso wrote:\n"
@@ -126,4 +152,4 @@
  "\n"
  Rob
 
-10a5eea43d2e969f6be6e136ca88ab49f30ea6c18277f2398754a1103bb02ddb
+b7b6910848c831b2ab02ebde055e901e447558a96facb269e9ec02c6a7d2d3d7

diff --git a/a/1.txt b/N2/1.txt
index dd2036e..fa868ab 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -4,7 +4,7 @@ On 09/08/2015 02:30 AM, Tomeu Vizoso wrote:
 >>> Hello,
 >>>
 >>> I have a problem with the panel on my Tegra Chromebook taking longer
->>> than expected to be ready during boot (Stéphane Marchesin reported what
+>>> than expected to be ready during boot (Stéphane Marchesin reported what
 >>> is basically the same issue in [0]), and have looked into ordered
 >>> probing as a better way of solving this than moving nodes around in the
 >>> DT or playing with initcall levels and linking order.
diff --git a/a/content_digest b/N2/content_digest
index 13b1756..e5a03d1 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -3,7 +3,7 @@
  "ref\0CAAObsKDUzk-9H2_VrVmbc=ZeRaknGcjTMY3Mauh3JVZxLz4CiA@mail.gmail.com\0"
  "From\0Rob Herring <robh@kernel.org>\0"
  "Subject\0Re: [PATCH v4 0/22] On-demand device probing\0"
- "Date\0Tue, 8 Sep 2015 20:33:25 -0500\0"
+ "Date\0Wed, 09 Sep 2015 01:33:25 +0000\0"
  "To\0Tomeu Vizoso <tomeu.vizoso@collabora.com>\0"
  "Cc\0linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>"
   Stephen Warren <swarren@wwwdotorg.org>
@@ -31,7 +31,7 @@
  ">>> Hello,\n"
  ">>>\n"
  ">>> I have a problem with the panel on my Tegra Chromebook taking longer\n"
- ">>> than expected to be ready during boot (St\303\251phane Marchesin reported what\n"
+ ">>> than expected to be ready during boot (St\303\203\302\251phane Marchesin reported what\n"
  ">>> is basically the same issue in [0]), and have looked into ordered\n"
  ">>> probing as a better way of solving this than moving nodes around in the\n"
  ">>> DT or playing with initcall levels and linking order.\n"
@@ -126,4 +126,4 @@
  "\n"
  Rob
 
-10a5eea43d2e969f6be6e136ca88ab49f30ea6c18277f2398754a1103bb02ddb
+b4da35dc012b1223207f5f1e6147c8652081cb90942ffc003fb7056b0b5ebfa9

diff --git a/a/1.txt b/N3/1.txt
index dd2036e..fa37ccb 100644
--- a/a/1.txt
+++ b/N3/1.txt
@@ -4,7 +4,7 @@ On 09/08/2015 02:30 AM, Tomeu Vizoso wrote:
 >>> Hello,
 >>>
 >>> I have a problem with the panel on my Tegra Chromebook taking longer
->>> than expected to be ready during boot (Stéphane Marchesin reported what
+>>> than expected to be ready during boot (St?phane Marchesin reported what
 >>> is basically the same issue in [0]), and have looked into ordered
 >>> probing as a better way of solving this than moving nodes around in the
 >>> DT or playing with initcall levels and linking order.
diff --git a/a/content_digest b/N3/content_digest
index 13b1756..b2fd452 100644
--- a/a/content_digest
+++ b/N3/content_digest
@@ -1,28 +1,10 @@
  "ref\01441628627-5143-1-git-send-email-tomeu.vizoso@collabora.com\0"
  "ref\0CAL_Jsq+E31JaPcp5ELS_ztSqgSrK7U4OzB9xNcNz01Ayrrm+Yg@mail.gmail.com\0"
  "ref\0CAAObsKDUzk-9H2_VrVmbc=ZeRaknGcjTMY3Mauh3JVZxLz4CiA@mail.gmail.com\0"
- "From\0Rob Herring <robh@kernel.org>\0"
- "Subject\0Re: [PATCH v4 0/22] On-demand device probing\0"
+ "From\0robh@kernel.org (Rob Herring)\0"
+ "Subject\0[PATCH v4 0/22] On-demand device probing\0"
  "Date\0Tue, 8 Sep 2015 20:33:25 -0500\0"
- "To\0Tomeu Vizoso <tomeu.vizoso@collabora.com>\0"
- "Cc\0linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>"
-  Stephen Warren <swarren@wwwdotorg.org>
-  Javier Martinez Canillas <javier@osg.samsung.com>
-  Mark Brown <broonie@kernel.org>
-  Thierry Reding <thierry.reding@gmail.com>
-  Rafael J. Wysocki <rjw@rjwysocki.net>
-  linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org>
-  Dmitry Torokhov <dmitry.torokhov@gmail.com>
-  devicetree@vger.kernel.org <devicetree@vger.kernel.org>
-  Linus Walleij <linus.walleij@linaro.org>
-  linux-acpi@vger.kernel.org <linux-acpi@vger.kernel.org>
-  Arnd Bergmann <arnd@arndb.de>
-  linux-fbdev@vger.kernel.org <linux-fbdev@vger.kernel.org>
-  Linux USB List <linux-usb@vger.kernel.org>
-  Felipe Balbi <balbi@ti.com>
-  Linux PWM List <linux-pwm@vger.kernel.org>
- " Terje Bergstr\303\266m <tbergstrom@nvidia.com>"
- " Greg Kroah-Hartman <gregkh@linuxfoundation.org>\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "On 09/08/2015 02:30 AM, Tomeu Vizoso wrote:\n"
@@ -31,7 +13,7 @@
  ">>> Hello,\n"
  ">>>\n"
  ">>> I have a problem with the panel on my Tegra Chromebook taking longer\n"
- ">>> than expected to be ready during boot (St\303\251phane Marchesin reported what\n"
+ ">>> than expected to be ready during boot (St?phane Marchesin reported what\n"
  ">>> is basically the same issue in [0]), and have looked into ordered\n"
  ">>> probing as a better way of solving this than moving nodes around in the\n"
  ">>> DT or playing with initcall levels and linking order.\n"
@@ -126,4 +108,4 @@
  "\n"
  Rob
 
-10a5eea43d2e969f6be6e136ca88ab49f30ea6c18277f2398754a1103bb02ddb
+35c2c9985b8d47c1da4ad12038e9a5e69c57e5d190a7f1e3cbba2e14910bf65e

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.