All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <560C993D.8090308@redhat.com>

diff --git a/a/1.txt b/N1/1.txt
index c222573..56bcf37 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -48,7 +48,7 @@ Here is where I think we are:
       ourselves about the spec in any way.  This was an essential step in
       order to make IP rules clear.
 
-   -- There is a mailing list set up (dsd at acpica.org), originally set up as
+   -- There is a mailing list set up (dsd@acpica.org), originally set up as
       the starting point for a review process.  I have recently started up
       some discussion there on what needs to be submitted.  I will soon be
       posting updates to the discussion to lay out proposed review processes
@@ -57,7 +57,7 @@ Here is where I think we are:
       that can be found here: https://lists.acpica.org/mailman/listinfo/dsd
 
       In the meantime, device property definition review can start occurring
-      on the dsd at acpica.org list with the caveat that process is still being
+      on the dsd@acpica.org list with the caveat that process is still being
       defined.  At least if things are put in the email archive, we've got a
       starting point.
 
@@ -78,7 +78,7 @@ Here is where I think we are:
 
 What needs to happen next?
 
-   -- First, finalize the review process (discussion on dsd at apcica.org).
+   -- First, finalize the review process (discussion on dsd@apcica.org).
 
    -- Second, finalize the reviewers (discussion on dsd@).
 
@@ -152,7 +152,7 @@ we as a community decide on something better.
 >> matched via PRP0001 or a newly-allocated HID.
 >>
 >> The driver, as the patch was posted, *does* have the same set of
->> properties with the same meanings ? because anything else would be
+>> properties with the same meanings — because anything else would be
 >> insane.
 > 
 > Having the same set of properties makes sense. But not documenting them
@@ -211,7 +211,7 @@ both questions, correct?
 > "canonical" implementation).
 
 Agreed.  This is what Charles, Rafael and I have started discussing on the
-dsd at acpica.org mailing list.  I have proposed a formalism for describing
+dsd@acpica.org mailing list.  I have proposed a formalism for describing
 properties (actively being revised) and we have some basic process proposals
 being discussed.  More voices are needed; we're just starting to get things
 moving after they've been in stasis so long.
@@ -225,7 +225,7 @@ things to be vetted and I think we can have a decent methodology in place.
 
 >> But in a world where people *are* going to go off and do their own
 >> insane thing, we really might as well let them use the *same* thing
->> that we already had ? in as many cases as possible ? rather than
+>> that we already had — in as many cases as possible — rather than
 >> actually *making* them come up with a new insane thing all of their
 >> very own.
 > 
@@ -248,5 +248,5 @@ al
 Al Stone
 Software Engineer
 Red Hat, Inc.
-ahs3 at redhat.com
+ahs3@redhat.com
 -----------------------------------
diff --git a/a/content_digest b/N1/content_digest
index 70bc327..58b7e7b 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -9,10 +9,20 @@
  "ref\020150924151546.GJ13823@e104818-lin.cambridge.arm.com\0"
  "ref\01443118238.74600.117.camel@infradead.org\0"
  "ref\020150925152848.GQ13823@e104818-lin.cambridge.arm.com\0"
- "From\0ahs3@redhat.com (Al Stone)\0"
- "Subject\0[PATCH 2/2] Convert smsc911x to use ACPI as well as DT\0"
+ "From\0Al Stone <ahs3@redhat.com>\0"
+ "Subject\0Re: [PATCH 2/2] Convert smsc911x to use ACPI as well as DT\0"
  "Date\0Wed, 30 Sep 2015 20:23:57 -0600\0"
- "To\0linux-arm-kernel@lists.infradead.org\0"
+ "To\0Catalin Marinas <catalin.marinas@arm.com>"
+ " David Woodhouse <dwmw2@infradead.org>\0"
+ "Cc\0steve.glendinning@shawell.net"
+  netdev@vger.kernel.org
+  Rafael J. Wysocki <rafael.j.wysocki@intel.com>
+  Jeremy Linton <jeremy.linton@arm.com>
+  Hanjun Guo <hanjun.guo@linaro.org>
+  Suravee.Suthikulpanit@amd.com
+  grant.likely@linaro.org
+  linux-arm-kernel@lists.infradead.org
+ " Charles Garcia-Tobin <Charles.Garcia-Tobin@arm.com>\0"
  "\00:1\0"
  "b\0"
  "Adding Charles Garcia-Tobin from ARM....\n"
@@ -65,7 +75,7 @@
  "      ourselves about the spec in any way.  This was an essential step in\n"
  "      order to make IP rules clear.\n"
  "\n"
- "   -- There is a mailing list set up (dsd at acpica.org), originally set up as\n"
+ "   -- There is a mailing list set up (dsd@acpica.org), originally set up as\n"
  "      the starting point for a review process.  I have recently started up\n"
  "      some discussion there on what needs to be submitted.  I will soon be\n"
  "      posting updates to the discussion to lay out proposed review processes\n"
@@ -74,7 +84,7 @@
  "      that can be found here: https://lists.acpica.org/mailman/listinfo/dsd\n"
  "\n"
  "      In the meantime, device property definition review can start occurring\n"
- "      on the dsd at acpica.org list with the caveat that process is still being\n"
+ "      on the dsd@acpica.org list with the caveat that process is still being\n"
  "      defined.  At least if things are put in the email archive, we've got a\n"
  "      starting point.\n"
  "\n"
@@ -95,7 +105,7 @@
  "\n"
  "What needs to happen next?\n"
  "\n"
- "   -- First, finalize the review process (discussion on dsd at apcica.org).\n"
+ "   -- First, finalize the review process (discussion on dsd@apcica.org).\n"
  "\n"
  "   -- Second, finalize the reviewers (discussion on dsd@).\n"
  "\n"
@@ -169,7 +179,7 @@
  ">> matched via PRP0001 or a newly-allocated HID.\n"
  ">>\n"
  ">> The driver, as the patch was posted, *does* have the same set of\n"
- ">> properties with the same meanings ? because anything else would be\n"
+ ">> properties with the same meanings \342\200\224 because anything else would be\n"
  ">> insane.\n"
  "> \n"
  "> Having the same set of properties makes sense. But not documenting them\n"
@@ -228,7 +238,7 @@
  "> \"canonical\" implementation).\n"
  "\n"
  "Agreed.  This is what Charles, Rafael and I have started discussing on the\n"
- "dsd at acpica.org mailing list.  I have proposed a formalism for describing\n"
+ "dsd@acpica.org mailing list.  I have proposed a formalism for describing\n"
  "properties (actively being revised) and we have some basic process proposals\n"
  "being discussed.  More voices are needed; we're just starting to get things\n"
  "moving after they've been in stasis so long.\n"
@@ -242,7 +252,7 @@
  "\n"
  ">> But in a world where people *are* going to go off and do their own\n"
  ">> insane thing, we really might as well let them use the *same* thing\n"
- ">> that we already had ? in as many cases as possible ? rather than\n"
+ ">> that we already had \342\200\224 in as many cases as possible \342\200\224 rather than\n"
  ">> actually *making* them come up with a new insane thing all of their\n"
  ">> very own.\n"
  "> \n"
@@ -265,7 +275,7 @@
  "Al Stone\n"
  "Software Engineer\n"
  "Red Hat, Inc.\n"
- "ahs3 at redhat.com\n"
+ "ahs3@redhat.com\n"
  -----------------------------------
 
-6ce3f75ec54ef8dfec03623b01dcf1f0f8962ed60ea9cdcaf645d85b368f916f
+b1e62a9417978e92b6462007fa0b292bea3aae96c315559dabc487a962c69975

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.