All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <7ce29bba-485c-b063-961a-3a745718357f@arm.com>

diff --git a/a/1.txt b/N1/1.txt
index 0aa3128..60508d7 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -6,9 +6,9 @@ On 08/11/17 15:19, Guillaume Tucker wrote:
 >>> On Tue, Nov 07, 2017 at 10:12:59AM +0000, Jon Hunter wrote:
 >>>> On 06/11/17 19:17, Mark Brown wrote:
 >>>
->>>>>>     multi_v7_defconfig:
->>>>>>         tegra124-nyan-big:
->>>>>>             lab-collabora: failing since 2 days (last pass: 
+>>>>>> ??? multi_v7_defconfig:
+>>>>>> ??????? tegra124-nyan-big:
+>>>>>> ??????????? lab-collabora: failing since 2 days (last pass: 
 >>>>>> next-20171102 - first fail: next-20171103)
 >>>
 >>>> Thanks for the report. I have been looking into a failure on nyan-big
@@ -25,15 +25,15 @@ On 08/11/17 15:19, Guillaume Tucker wrote:
 >>> (not CCing Johannes yet)
 >>
 >> Please take this with a pinch of salt, I'm now running some extra
->> boot tests to prove it.  If you look at this log, all the boots
->> passed which is a bit suspicious.  I did build and boot the
+>> boot tests to prove it.? If you look at this log, all the boots
+>> passed which is a bit suspicious.? I did build and boot the
 >> revision it found with multi_v7_defconfig on tegra124 and it
 >> passed, so it looks like this commit may not have anything to do
->> with the boot failure.  The automated bisection is still experimental.
+>> with the boot failure.? The automated bisection is still experimental.
 >>
 >> Passing LAVA boot test with this revision:
 >>
->>   https://lava.collabora.co.uk/scheduler/job/976375
+>> ? https://lava.collabora.co.uk/scheduler/job/976375
 >>
 >> I've started a slightly different bisection job now on
 >> next-20171107 and the common ancestor between next and mainline,
@@ -42,38 +42,38 @@ On 08/11/17 15:19, Guillaume Tucker wrote:
 > After a few more automated bisection attempts and a bug fix in
 > LAVA, I've now found at least one potentially breaking commit:
 > 
->    commit d89e2378a97fafdc74cbf997e7c88af75b81610a
->    Author: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
->    Date:   Thu Oct 12 16:56:14 2017 +0100
+>  ? commit d89e2378a97fafdc74cbf997e7c88af75b81610a
+>  ? Author: Robin Murphy <robin.murphy@arm.com>
+>  ? Date:?? Thu Oct 12 16:56:14 2017 +0100
 > 
->        drivers: flag buses which demand DMA configuration
+>  ????? drivers: flag buses which demand DMA configuration
 > 
 > 
 > I've run some boot tests manually with this revision and then
 > also after reverting it in-place, these respectively failed and
 > passed:
 > 
->    * d89e2378, failed:
->      https://lava.collabora.co.uk/scheduler/job/978968
+>  ? * d89e2378, failed:
+>  ??? https://lava.collabora.co.uk/scheduler/job/978968
 > 
->    * d89e2378 reverted, passed:
->      https://lava.collabora.co.uk/scheduler/job/978969
+>  ? * d89e2378 reverted, passed:
+>  ??? https://lava.collabora.co.uk/scheduler/job/978969
 > 
 > 
 > I then went on and tried the same but on top of next-20171108 and
 > found that they both failed
 > 
->    * next-20171108, failed:
->      https://lava.collabora.co.uk/scheduler/job/979063
+>  ? * next-20171108, failed:
+>  ??? https://lava.collabora.co.uk/scheduler/job/979063
 > 
->    * next-20171108 with d89e2378 reverted, failed as well:
->      https://lava.collabora.co.uk/scheduler/job/979167
+>  ? * next-20171108 with d89e2378 reverted, failed as well:
+>  ??? https://lava.collabora.co.uk/scheduler/job/979167
 > 
 > 
 > So this shows there is almost certainly another offending commit
-> in -next.  The errors in both cases are not quite the same, the
+> in -next.? The errors in both cases are not quite the same, the
 > last one is triggered by a BUG whereas the first one is a NULL
-> pointer (I haven't looked any further).  Also I don't think
+> pointer (I haven't looked any further).? Also I don't think
 > there's any fix for d89e2378a97fafdc74cbf997e7c88af75b81610a
 > which is currently still in next.
 
@@ -90,7 +90,7 @@ Robin.
 > 
 > Note: This happens to be a very good example of running a
 > kernelci.org bisection on a real issue, it's quite a bit of a
-> pipe cleaner.  I'll now see if there's a way to bisect what looks
+> pipe cleaner.? I'll now see if there's a way to bisect what looks
 > like another breaking change in-between.
 > 
 > Guillaume
\ No newline at end of file
diff --git a/a/content_digest b/N1/content_digest
index 8d03eb8..d330e2d 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -17,27 +17,16 @@
   "ref\000613bcd63-a215-acbe-9150-c1495f7604f6\@collabora.com\0"
 ]
 [
-  "ref\000613bcd63-a215-acbe-9150-c1495f7604f6-ZGY8ohtN/8qB+jHODAdFcQ\@public.gmane.org\0"
+  "From\0robin.murphy\@arm.com (Robin Murphy)\0"
 ]
 [
-  "From\0Robin Murphy <robin.murphy-5wv7dgnIgG8\@public.gmane.org>\0"
-]
-[
-  "Subject\0Re: next/master boot: 273 boots: 63 failed, 209 passed with 1 untried/unknown (next-20171106)\0"
+  "Subject\0next/master boot: 273 boots: 63 failed, 209 passed with 1 untried/unknown (next-20171106)\0"
 ]
 [
   "Date\0Wed, 8 Nov 2017 15:55:38 +0000\0"
 ]
 [
-  "To\0Guillaume Tucker <guillaume.tucker-ZGY8ohtN/8qB+jHODAdFcQ\@public.gmane.org>",
-  " Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A\@public.gmane.org>",
-  " Jon Hunter <jonathanh-DDmLM1+adcrQT0dZR+AlfA\@public.gmane.org>\0"
-]
-[
-  "Cc\0linux-tegra-u79uwXL29TY76Z2rM5mHXA\@public.gmane.org",
-  " linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r\@public.gmane.org",
-  " kernelci.org bot <bot-ssFOTAMYnuFg9hUCZPvPmw\@public.gmane.org>",
-  " kernel-build-reports-cunTk1MwBs8s++Sfvej+rw\@public.gmane.org\0"
+  "To\0linux-arm-kernel\@lists.infradead.org\0"
 ]
 [
   "\0000:1\0"
@@ -54,9 +43,9 @@
   ">>> On Tue, Nov 07, 2017 at 10:12:59AM +0000, Jon Hunter wrote:\n",
   ">>>> On 06/11/17 19:17, Mark Brown wrote:\n",
   ">>>\n",
-  ">>>>>> \302\240\302\240\302\240 multi_v7_defconfig:\n",
-  ">>>>>> \302\240\302\240\302\240\302\240\302\240\302\240\302\240 tegra124-nyan-big:\n",
-  ">>>>>> \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240 lab-collabora: failing since 2 days (last pass: \n",
+  ">>>>>> ??? multi_v7_defconfig:\n",
+  ">>>>>> ??????? tegra124-nyan-big:\n",
+  ">>>>>> ??????????? lab-collabora: failing since 2 days (last pass: \n",
   ">>>>>> next-20171102 - first fail: next-20171103)\n",
   ">>>\n",
   ">>>> Thanks for the report. I have been looking into a failure on nyan-big\n",
@@ -73,15 +62,15 @@
   ">>> (not CCing Johannes yet)\n",
   ">>\n",
   ">> Please take this with a pinch of salt, I'm now running some extra\n",
-  ">> boot tests to prove it.\302\240 If you look at this log, all the boots\n",
-  ">> passed which is a bit suspicious.\302\240 I did build and boot the\n",
+  ">> boot tests to prove it.? If you look at this log, all the boots\n",
+  ">> passed which is a bit suspicious.? I did build and boot the\n",
   ">> revision it found with multi_v7_defconfig on tegra124 and it\n",
   ">> passed, so it looks like this commit may not have anything to do\n",
-  ">> with the boot failure.\302\240 The automated bisection is still experimental.\n",
+  ">> with the boot failure.? The automated bisection is still experimental.\n",
   ">>\n",
   ">> Passing LAVA boot test with this revision:\n",
   ">>\n",
-  ">> \302\240 https://lava.collabora.co.uk/scheduler/job/976375\n",
+  ">> ? https://lava.collabora.co.uk/scheduler/job/976375\n",
   ">>\n",
   ">> I've started a slightly different bisection job now on\n",
   ">> next-20171107 and the common ancestor between next and mainline,\n",
@@ -90,38 +79,38 @@
   "> After a few more automated bisection attempts and a bug fix in\n",
   "> LAVA, I've now found at least one potentially breaking commit:\n",
   "> \n",
-  ">  \302\240 commit d89e2378a97fafdc74cbf997e7c88af75b81610a\n",
-  ">  \302\240 Author: Robin Murphy <robin.murphy-5wv7dgnIgG8\@public.gmane.org>\n",
-  ">  \302\240 Date:\302\240\302\240 Thu Oct 12 16:56:14 2017 +0100\n",
+  ">  ? commit d89e2378a97fafdc74cbf997e7c88af75b81610a\n",
+  ">  ? Author: Robin Murphy <robin.murphy\@arm.com>\n",
+  ">  ? Date:?? Thu Oct 12 16:56:14 2017 +0100\n",
   "> \n",
-  ">  \302\240\302\240\302\240\302\240\302\240 drivers: flag buses which demand DMA configuration\n",
+  ">  ????? drivers: flag buses which demand DMA configuration\n",
   "> \n",
   "> \n",
   "> I've run some boot tests manually with this revision and then\n",
   "> also after reverting it in-place, these respectively failed and\n",
   "> passed:\n",
   "> \n",
-  ">  \302\240 * d89e2378, failed:\n",
-  ">  \302\240\302\240\302\240 https://lava.collabora.co.uk/scheduler/job/978968\n",
+  ">  ? * d89e2378, failed:\n",
+  ">  ??? https://lava.collabora.co.uk/scheduler/job/978968\n",
   "> \n",
-  ">  \302\240 * d89e2378 reverted, passed:\n",
-  ">  \302\240\302\240\302\240 https://lava.collabora.co.uk/scheduler/job/978969\n",
+  ">  ? * d89e2378 reverted, passed:\n",
+  ">  ??? https://lava.collabora.co.uk/scheduler/job/978969\n",
   "> \n",
   "> \n",
   "> I then went on and tried the same but on top of next-20171108 and\n",
   "> found that they both failed\n",
   "> \n",
-  ">  \302\240 * next-20171108, failed:\n",
-  ">  \302\240\302\240\302\240 https://lava.collabora.co.uk/scheduler/job/979063\n",
+  ">  ? * next-20171108, failed:\n",
+  ">  ??? https://lava.collabora.co.uk/scheduler/job/979063\n",
   "> \n",
-  ">  \302\240 * next-20171108 with d89e2378 reverted, failed as well:\n",
-  ">  \302\240\302\240\302\240 https://lava.collabora.co.uk/scheduler/job/979167\n",
+  ">  ? * next-20171108 with d89e2378 reverted, failed as well:\n",
+  ">  ??? https://lava.collabora.co.uk/scheduler/job/979167\n",
   "> \n",
   "> \n",
   "> So this shows there is almost certainly another offending commit\n",
-  "> in -next.\302\240 The errors in both cases are not quite the same, the\n",
+  "> in -next.? The errors in both cases are not quite the same, the\n",
   "> last one is triggered by a BUG whereas the first one is a NULL\n",
-  "> pointer (I haven't looked any further).\302\240 Also I don't think\n",
+  "> pointer (I haven't looked any further).? Also I don't think\n",
   "> there's any fix for d89e2378a97fafdc74cbf997e7c88af75b81610a\n",
   "> which is currently still in next.\n",
   "\n",
@@ -138,10 +127,10 @@
   "> \n",
   "> Note: This happens to be a very good example of running a\n",
   "> kernelci.org bisection on a real issue, it's quite a bit of a\n",
-  "> pipe cleaner.\302\240 I'll now see if there's a way to bisect what looks\n",
+  "> pipe cleaner.? I'll now see if there's a way to bisect what looks\n",
   "> like another breaking change in-between.\n",
   "> \n",
   "> Guillaume"
 ]
 
-fe77e74e9ea9f54855e301365ad73332172f8ec9e4065a50988062bfae90aba4
+ff307691bceb393ad24d12fb684c962a29097ad99b4c64ed5be6a6fce4d4aad0

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.