All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <2819798.f0KhjY3UAe@wuerfel>

diff --git a/a/1.txt b/N1/1.txt
index 873add6..ad0ec9d 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -100,19 +100,3 @@ struct timespec {
 This is very similar to c, but trades the problem I described
 above for a dependency on a gcc extension that is not part of
 C11 or any earlier standard.
-
-
-From the kernel's point of view, b), c) and d) can all be
-treated the same for output data, as we only ever pass back
-normalized timespec structures that have zeroes in the upper
-bits of timespec. However, for input to the kernel, we would
-require an extra conditional on 64-bit kernels to decide whether
-we ignore the upper bits (doing tv->tv_nsec &= 0xffffffff) or 
-a structure that has the upper bits set  needs to cause EINVAL.
-We could still do that in get_timespec() if we decide to not to
-go with a).
-
-See also https://lwn.net/Articles/457089/ for an earlier discussion
-on the topic when debating the x32 ABI.
-
-	Arnd
diff --git a/a/content_digest b/N1/content_digest
index 8fd6150..c1a3fb0 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -135,22 +135,6 @@
  "\n"
  "This is very similar to c, but trades the problem I described\n"
  "above for a dependency on a gcc extension that is not part of\n"
- "C11 or any earlier standard.\n"
- "\n"
- "\n"
- "From the kernel's point of view, b), c) and d) can all be\n"
- "treated the same for output data, as we only ever pass back\n"
- "normalized timespec structures that have zeroes in the upper\n"
- "bits of timespec. However, for input to the kernel, we would\n"
- "require an extra conditional on 64-bit kernels to decide whether\n"
- "we ignore the upper bits (doing tv->tv_nsec &= 0xffffffff) or \n"
- "a structure that has the upper bits set  needs to cause EINVAL.\n"
- "We could still do that in get_timespec() if we decide to not to\n"
- "go with a).\n"
- "\n"
- "See also https://lwn.net/Articles/457089/ for an earlier discussion\n"
- "on the topic when debating the x32 ABI.\n"
- "\n"
- "\tArnd"
+ C11 or any earlier standard.
 
-a97c2a2062b2c37a3d47627284cebe42c69f9b717c4a7807ebb2c399e48ff351
+3de44addc6b89c375cb25007bdbc6d9c82f1372cb5a9e94d9b454e5f19c65814

diff --git a/a/1.txt b/N2/1.txt
index 873add6..2eeba37 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -102,7 +102,7 @@ above for a dependency on a gcc extension that is not part of
 C11 or any earlier standard.
 
 
-From the kernel's point of view, b), c) and d) can all be
+>From the kernel's point of view, b), c) and d) can all be
 treated the same for output data, as we only ever pass back
 normalized timespec structures that have zeroes in the upper
 bits of timespec. However, for input to the kernel, we would
diff --git a/a/content_digest b/N2/content_digest
index 8fd6150..a5850cc 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -5,31 +5,29 @@
  "Subject\0Re: [Y2038] [PATCH 04/11] posix timers:Introduce the 64bit methods with timespec64 type for k_clock structure\0"
  "Date\0Tue, 21 Apr 2015 17:40:32 +0200\0"
  "To\0Thomas Gleixner <tglx@linutronix.de>\0"
- "Cc\0y2038@lists.linaro.org"
-  Baolin Wang <baolin.wang@linaro.org>
-  pang.xunlei@linaro.org
+ "Cc\0pang.xunlei@linaro.org"
   peterz@infradead.org
-  benh@kernel.crashing.org
   heiko.carstens@de.ibm.com
   paulus@samba.org
   cl@linux.com
   heenasirwani@gmail.com
   linux-arch@vger.kernel.org
   linux-s390@vger.kernel.org
-  mpe@ellerman.id.au
+  y2038@lists.linaro.org
   rafael.j.wysocki@intel.com
   ahh@google.com
   fweisbec@gmail.com
   pjt@google.com
   riel@redhat.com
   richardcochran@gmail.com
-  schwidefsky@de.ibm.com
+  tj@kernel.org
   john.stultz@linaro.org
   rth@twiddle.net
+  Baolin Wang <baolin.wang@linaro.org>
   gregkh@linuxfoundation.org
   linux-kernel@vger.kernel.org
   netdev@vger.kernel.org
-  tj@kernel.org
+  schwidefsky@de.ibm.com
   linux390@de.ibm.com
  " linuxppc-dev@lists.ozlabs.org\0"
  "\00:1\0"
@@ -138,7 +136,7 @@
  "C11 or any earlier standard.\n"
  "\n"
  "\n"
- "From the kernel's point of view, b), c) and d) can all be\n"
+ ">From the kernel's point of view, b), c) and d) can all be\n"
  "treated the same for output data, as we only ever pass back\n"
  "normalized timespec structures that have zeroes in the upper\n"
  "bits of timespec. However, for input to the kernel, we would\n"
@@ -153,4 +151,4 @@
  "\n"
  "\tArnd"
 
-a97c2a2062b2c37a3d47627284cebe42c69f9b717c4a7807ebb2c399e48ff351
+7903f82cc8f668d291a145c3fb9dda5b1afaae02a9bd97af319b949a127abdaf

diff --git a/a/1.txt b/N3/1.txt
index 873add6..2eeba37 100644
--- a/a/1.txt
+++ b/N3/1.txt
@@ -102,7 +102,7 @@ above for a dependency on a gcc extension that is not part of
 C11 or any earlier standard.
 
 
-From the kernel's point of view, b), c) and d) can all be
+>From the kernel's point of view, b), c) and d) can all be
 treated the same for output data, as we only ever pass back
 normalized timespec structures that have zeroes in the upper
 bits of timespec. However, for input to the kernel, we would
diff --git a/a/content_digest b/N3/content_digest
index 8fd6150..7c6f10d 100644
--- a/a/content_digest
+++ b/N3/content_digest
@@ -138,7 +138,7 @@
  "C11 or any earlier standard.\n"
  "\n"
  "\n"
- "From the kernel's point of view, b), c) and d) can all be\n"
+ ">From the kernel's point of view, b), c) and d) can all be\n"
  "treated the same for output data, as we only ever pass back\n"
  "normalized timespec structures that have zeroes in the upper\n"
  "bits of timespec. However, for input to the kernel, we would\n"
@@ -153,4 +153,4 @@
  "\n"
  "\tArnd"
 
-a97c2a2062b2c37a3d47627284cebe42c69f9b717c4a7807ebb2c399e48ff351
+7cf2ba905bd1b627a413ebc181284f11f1a57e72ac1e7ea3c5bd06cec845a377

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.