All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20100519164534.GE1693@shareable.org>

diff --git a/a/1.txt b/N1/1.txt
index a2a4fc7..60ce49c 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,19 +1,19 @@
 Grant Likely wrote:
-> On Tue, May 18, 2010 at 5:57 AM, Nicolas Pitre <nico@fluxnic.net> wrote:
+> On Tue, May 18, 2010 at 5:57 AM, Nicolas Pitre <nico-vtqb6HGKxmzR7s880joybQ@public.gmane.org> wrote:
 > > On Tue, 18 May 2010, Jeremy Kerr wrote:
 > >
 > >> Hi Nicolas,
 > >>
 > >> > I think that, for the moment, it is best if the bootloader on already
 > >> > existing subarchitectures where DT is introduced still preserve the
-> >> > already existing ability to boot using ATAGs. ?This allows for the
+> >> > already existing ability to boot using ATAGs.  This allows for the
 > >> > testing and validation of the DT concept against the legacy ATAG method
 > >> > more easily.
 > >>
 > >> Just to clarify - by "still preserve the existing ability to use ATAGs" you
 > >> mean only for non-DT boot, right?
 > >
-> > Exact. ?Once a particular SOC family has no non-DT support anymore (due
+> > Exact.  Once a particular SOC family has no non-DT support anymore (due
 > > to being entirely new, or because people get really enthusiastic and
 > > fade out legacy machine specific init code completely) then and only
 > > then it might be logical to remove ATAG from the concerned bootloaders.
diff --git a/a/content_digest b/N1/content_digest
index 3fc3b17..82bc60b 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -3,28 +3,34 @@
  "ref\0201005181324.45701.jeremy.kerr@canonical.com\0"
  "ref\0alpine.LFD.2.00.1005180742500.12758@xanadu.home\0"
  "ref\0AANLkTinsOSI_TIc7Jyy4QFuFaS2d-fi0y3LMuITLyG3N@mail.gmail.com\0"
- "From\0jamie@shareable.org (Jamie Lokier)\0"
- "Subject\0Boot interface for device trees on ARM\0"
+ "ref\0AANLkTinsOSI_TIc7Jyy4QFuFaS2d-fi0y3LMuITLyG3N-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org\0"
+ "From\0Jamie Lokier <jamie-yetKDKU6eevNLxjTenLetw@public.gmane.org>\0"
+ "Subject\0Re: Boot interface for device trees on ARM\0"
  "Date\0Wed, 19 May 2010 17:45:34 +0100\0"
- "To\0linux-arm-kernel@lists.infradead.org\0"
+ "To\0Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>\0"
+ "Cc\0nicolas.pitre-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org"
+  Jeremy Kerr <jeremy.kerr-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
+  devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
+  linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
+ " Nicolas Pitre <nico-vtqb6HGKxmzR7s880joybQ@public.gmane.org>\0"
  "\00:1\0"
  "b\0"
  "Grant Likely wrote:\n"
- "> On Tue, May 18, 2010 at 5:57 AM, Nicolas Pitre <nico@fluxnic.net> wrote:\n"
+ "> On Tue, May 18, 2010 at 5:57 AM, Nicolas Pitre <nico-vtqb6HGKxmzR7s880joybQ@public.gmane.org> wrote:\n"
  "> > On Tue, 18 May 2010, Jeremy Kerr wrote:\n"
  "> >\n"
  "> >> Hi Nicolas,\n"
  "> >>\n"
  "> >> > I think that, for the moment, it is best if the bootloader on already\n"
  "> >> > existing subarchitectures where DT is introduced still preserve the\n"
- "> >> > already existing ability to boot using ATAGs. ?This allows for the\n"
+ "> >> > already existing ability to boot using ATAGs. \302\240This allows for the\n"
  "> >> > testing and validation of the DT concept against the legacy ATAG method\n"
  "> >> > more easily.\n"
  "> >>\n"
  "> >> Just to clarify - by \"still preserve the existing ability to use ATAGs\" you\n"
  "> >> mean only for non-DT boot, right?\n"
  "> >\n"
- "> > Exact. ?Once a particular SOC family has no non-DT support anymore (due\n"
+ "> > Exact. \302\240Once a particular SOC family has no non-DT support anymore (due\n"
  "> > to being entirely new, or because people get really enthusiastic and\n"
  "> > fade out legacy machine specific init code completely) then and only\n"
  "> > then it might be logical to remove ATAG from the concerned bootloaders.\n"
@@ -81,4 +87,4 @@
  "\n"
  -- Jamie
 
-807604a97cef7bd15d7c9fedaeaedff5d70f522fbfd120ec793a7cc26a4069d7
+ce569a76d9e7868c7ee5bb9e505d78c3f4c7568d10f7c3660522c0fa27229155

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.