All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <Y9GsAOPMVX4qGero@spud>

diff --git a/N1/1.1.hdr b/N1/1.1.hdr
new file mode 100644
index 0000000..149ab5e
--- /dev/null
+++ b/N1/1.1.hdr
@@ -0,0 +1,3 @@
+Content-Type: text/plain; charset=utf-8
+Content-Disposition: inline
+Content-Transfer-Encoding: quoted-printable
diff --git a/a/1.txt b/N1/1.1.txt
similarity index 87%
rename from a/1.txt
rename to N1/1.1.txt
index 6c9ceb7..3819470 100644
--- a/a/1.txt
+++ b/N1/1.1.txt
@@ -42,16 +42,16 @@ On Wed, Jan 25, 2023 at 09:38:00PM +0000, Jessica Clarke wrote:
 > 
 > For implementations of unratified extensions you both have to enable
 > them with -menable-experimental-extensions and have to explicitly
-> specify the version in the -march string specifically so this isn?t a
+> specify the version in the -march string specifically so this isn’t a
 > concern. Only once ratified can you use the unversioned extension,
 > which is implicitly the ratified version (ignoring the whole i2p0 vs
 > i2p1 fiasco).
 
 Ahh, thanks for the clarification Jess.
 
-> But no, you probably don?t want experimental implementations, which can
-> exist when the ratified version is implemented in theory (so there?s no
-> compatibility concern based on ISA changes) but isn?t deemed
+> But no, you probably don’t want experimental implementations, which can
+> exist when the ratified version is implemented in theory (so there’s no
+> compatibility concern based on ISA changes) but isn’t deemed
 > production-ready (e.g. potential ABI instability in the case of
 > something like V).
 
@@ -60,11 +60,3 @@ While the vector extension might be okay in that regard, another
 extension well not be okay to use the "unversioned" experimental version
 of. Sounds like removing that option and picking the version of clang
 that adds the actual implementation is a better approach, at least IMO.
-
--------------- next part --------------
-A non-text attachment was scrubbed...
-Name: signature.asc
-Type: application/pgp-signature
-Size: 228 bytes
-Desc: not available
-URL: <http://lists.infradead.org/pipermail/kvm-riscv/attachments/20230125/a31ba3da/attachment-0001.sig>
diff --git a/N1/1.2.bin b/N1/1.2.bin
new file mode 100644
index 0000000..7860365
--- /dev/null
+++ b/N1/1.2.bin
@@ -0,0 +1,7 @@
+-----BEGIN PGP SIGNATURE-----
+
+iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCY9GsAAAKCRB4tDGHoIJi
+0hqFAQC48XA84lz48uhvAtpzLEHeMOU2tUpSJ8GlckABIXQCJwEA3wPARCef7sAh
+co6sjKqf4Skq3blkPVYO104tRYo0AAc=
+=bxFQ
+-----END PGP SIGNATURE-----
diff --git a/N1/1.2.hdr b/N1/1.2.hdr
new file mode 100644
index 0000000..5e5352c
--- /dev/null
+++ b/N1/1.2.hdr
@@ -0,0 +1 @@
+Content-Type: application/pgp-signature; name="signature.asc"
diff --git a/N1/2.hdr b/N1/2.hdr
new file mode 100644
index 0000000..4b86001
--- /dev/null
+++ b/N1/2.hdr
@@ -0,0 +1,4 @@
+Content-Type: text/plain; charset="us-ascii"
+MIME-Version: 1.0
+Content-Transfer-Encoding: 7bit
+Content-Disposition: inline
diff --git a/N1/2.txt b/N1/2.txt
new file mode 100644
index 0000000..e409076
--- /dev/null
+++ b/N1/2.txt
@@ -0,0 +1,4 @@
+_______________________________________________
+linux-riscv mailing list
+linux-riscv@lists.infradead.org
+http://lists.infradead.org/mailman/listinfo/linux-riscv
diff --git a/a/content_digest b/N1/content_digest
index 2cbad83..e1ba22e 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -3,10 +3,22 @@
  "ref\0Y9GZbVrZxEZAraVu@spud\0"
  "ref\008DF16C6-1D76-4FBE-871C-3A37C5349C87@jrtc27.com\0"
  "From\0Conor Dooley <conor@kernel.org>\0"
- "Subject\0[PATCH -next v13 19/19] riscv: Enable Vector code to be built\0"
+ "Subject\0Re: [PATCH -next v13 19/19] riscv: Enable Vector code to be built\0"
  "Date\0Wed, 25 Jan 2023 22:24:00 +0000\0"
- "To\0kvm-riscv@lists.infradead.org\0"
- "\00:1\0"
+ "To\0Jessica Clarke <jrtc27@jrtc27.com>\0"
+ "Cc\0Andy Chiu <andy.chiu@sifive.com>"
+  linux-riscv <linux-riscv@lists.infradead.org>
+  Palmer Dabbelt <palmer@dabbelt.com>
+  Anup Patel <anup@brainfault.org>
+  Atish Patra <atishp@atishpatra.org>
+  kvm-riscv@lists.infradead.org
+  kvm@vger.kernel.org
+  Vineet Gupta <vineetg@rivosinc.com>
+  Greentime Hu <greentime.hu@sifive.com>
+  Guo Ren <guoren@linux.alibaba.com>
+  Paul Walmsley <paul.walmsley@sifive.com>
+ " Albert Ou <aou@eecs.berkeley.edu>\0"
+ "\02:1.1\0"
  "b\0"
  "On Wed, Jan 25, 2023 at 09:38:00PM +0000, Jessica Clarke wrote:\n"
  "> On 25 Jan 2023, at 21:04, Conor Dooley <conor@kernel.org> wrote:\n"
@@ -52,16 +64,16 @@
  "> \n"
  "> For implementations of unratified extensions you both have to enable\n"
  "> them with -menable-experimental-extensions and have to explicitly\n"
- "> specify the version in the -march string specifically so this isn?t a\n"
+ "> specify the version in the -march string specifically so this isn\342\200\231t a\n"
  "> concern. Only once ratified can you use the unversioned extension,\n"
  "> which is implicitly the ratified version (ignoring the whole i2p0 vs\n"
  "> i2p1 fiasco).\n"
  "\n"
  "Ahh, thanks for the clarification Jess.\n"
  "\n"
- "> But no, you probably don?t want experimental implementations, which can\n"
- "> exist when the ratified version is implemented in theory (so there?s no\n"
- "> compatibility concern based on ISA changes) but isn?t deemed\n"
+ "> But no, you probably don\342\200\231t want experimental implementations, which can\n"
+ "> exist when the ratified version is implemented in theory (so there\342\200\231s no\n"
+ "> compatibility concern based on ISA changes) but isn\342\200\231t deemed\n"
  "> production-ready (e.g. potential ABI instability in the case of\n"
  "> something like V).\n"
  "\n"
@@ -69,14 +81,22 @@
  "While the vector extension might be okay in that regard, another\n"
  "extension well not be okay to use the \"unversioned\" experimental version\n"
  "of. Sounds like removing that option and picking the version of clang\n"
- "that adds the actual implementation is a better approach, at least IMO.\n"
+ that adds the actual implementation is a better approach, at least IMO.
+ "\02:1.2\0"
+ "fn\0signature.asc\0"
+ "b\0"
+ "-----BEGIN PGP SIGNATURE-----\n"
  "\n"
- "-------------- next part --------------\n"
- "A non-text attachment was scrubbed...\n"
- "Name: signature.asc\n"
- "Type: application/pgp-signature\n"
- "Size: 228 bytes\n"
- "Desc: not available\n"
- URL: <http://lists.infradead.org/pipermail/kvm-riscv/attachments/20230125/a31ba3da/attachment-0001.sig>
+ "iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCY9GsAAAKCRB4tDGHoIJi\n"
+ "0hqFAQC48XA84lz48uhvAtpzLEHeMOU2tUpSJ8GlckABIXQCJwEA3wPARCef7sAh\n"
+ "co6sjKqf4Skq3blkPVYO104tRYo0AAc=\n"
+ "=bxFQ\n"
+ "-----END PGP SIGNATURE-----\n"
+ "\01:2\0"
+ "b\0"
+ "_______________________________________________\n"
+ "linux-riscv mailing list\n"
+ "linux-riscv@lists.infradead.org\n"
+ http://lists.infradead.org/mailman/listinfo/linux-riscv
 
-8f8c57fac0380acc8019016cf85a53698c4f0bd76385746e8c5e70ebf39d5593
+970ed43706e317a1811946a38cc97d488eabd02c35fa738804d50892fc75d06d

diff --git a/a/1.txt b/N2/1.txt
index 6c9ceb7..3819470 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -42,16 +42,16 @@ On Wed, Jan 25, 2023 at 09:38:00PM +0000, Jessica Clarke wrote:
 > 
 > For implementations of unratified extensions you both have to enable
 > them with -menable-experimental-extensions and have to explicitly
-> specify the version in the -march string specifically so this isn?t a
+> specify the version in the -march string specifically so this isn’t a
 > concern. Only once ratified can you use the unversioned extension,
 > which is implicitly the ratified version (ignoring the whole i2p0 vs
 > i2p1 fiasco).
 
 Ahh, thanks for the clarification Jess.
 
-> But no, you probably don?t want experimental implementations, which can
-> exist when the ratified version is implemented in theory (so there?s no
-> compatibility concern based on ISA changes) but isn?t deemed
+> But no, you probably don’t want experimental implementations, which can
+> exist when the ratified version is implemented in theory (so there’s no
+> compatibility concern based on ISA changes) but isn’t deemed
 > production-ready (e.g. potential ABI instability in the case of
 > something like V).
 
@@ -60,11 +60,3 @@ While the vector extension might be okay in that regard, another
 extension well not be okay to use the "unversioned" experimental version
 of. Sounds like removing that option and picking the version of clang
 that adds the actual implementation is a better approach, at least IMO.
-
--------------- next part --------------
-A non-text attachment was scrubbed...
-Name: signature.asc
-Type: application/pgp-signature
-Size: 228 bytes
-Desc: not available
-URL: <http://lists.infradead.org/pipermail/kvm-riscv/attachments/20230125/a31ba3da/attachment-0001.sig>
diff --git a/N2/2.bin b/N2/2.bin
new file mode 100644
index 0000000..7860365
--- /dev/null
+++ b/N2/2.bin
@@ -0,0 +1,7 @@
+-----BEGIN PGP SIGNATURE-----
+
+iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCY9GsAAAKCRB4tDGHoIJi
+0hqFAQC48XA84lz48uhvAtpzLEHeMOU2tUpSJ8GlckABIXQCJwEA3wPARCef7sAh
+co6sjKqf4Skq3blkPVYO104tRYo0AAc=
+=bxFQ
+-----END PGP SIGNATURE-----
diff --git a/N2/2.hdr b/N2/2.hdr
new file mode 100644
index 0000000..5e5352c
--- /dev/null
+++ b/N2/2.hdr
@@ -0,0 +1 @@
+Content-Type: application/pgp-signature; name="signature.asc"
diff --git a/a/content_digest b/N2/content_digest
index 2cbad83..36be844 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -3,10 +3,22 @@
  "ref\0Y9GZbVrZxEZAraVu@spud\0"
  "ref\008DF16C6-1D76-4FBE-871C-3A37C5349C87@jrtc27.com\0"
  "From\0Conor Dooley <conor@kernel.org>\0"
- "Subject\0[PATCH -next v13 19/19] riscv: Enable Vector code to be built\0"
+ "Subject\0Re: [PATCH -next v13 19/19] riscv: Enable Vector code to be built\0"
  "Date\0Wed, 25 Jan 2023 22:24:00 +0000\0"
- "To\0kvm-riscv@lists.infradead.org\0"
- "\00:1\0"
+ "To\0Jessica Clarke <jrtc27@jrtc27.com>\0"
+ "Cc\0Andy Chiu <andy.chiu@sifive.com>"
+  linux-riscv <linux-riscv@lists.infradead.org>
+  Palmer Dabbelt <palmer@dabbelt.com>
+  Anup Patel <anup@brainfault.org>
+  Atish Patra <atishp@atishpatra.org>
+  kvm-riscv@lists.infradead.org
+  kvm@vger.kernel.org
+  Vineet Gupta <vineetg@rivosinc.com>
+  Greentime Hu <greentime.hu@sifive.com>
+  Guo Ren <guoren@linux.alibaba.com>
+  Paul Walmsley <paul.walmsley@sifive.com>
+ " Albert Ou <aou@eecs.berkeley.edu>\0"
+ "\01:1\0"
  "b\0"
  "On Wed, Jan 25, 2023 at 09:38:00PM +0000, Jessica Clarke wrote:\n"
  "> On 25 Jan 2023, at 21:04, Conor Dooley <conor@kernel.org> wrote:\n"
@@ -52,16 +64,16 @@
  "> \n"
  "> For implementations of unratified extensions you both have to enable\n"
  "> them with -menable-experimental-extensions and have to explicitly\n"
- "> specify the version in the -march string specifically so this isn?t a\n"
+ "> specify the version in the -march string specifically so this isn\342\200\231t a\n"
  "> concern. Only once ratified can you use the unversioned extension,\n"
  "> which is implicitly the ratified version (ignoring the whole i2p0 vs\n"
  "> i2p1 fiasco).\n"
  "\n"
  "Ahh, thanks for the clarification Jess.\n"
  "\n"
- "> But no, you probably don?t want experimental implementations, which can\n"
- "> exist when the ratified version is implemented in theory (so there?s no\n"
- "> compatibility concern based on ISA changes) but isn?t deemed\n"
+ "> But no, you probably don\342\200\231t want experimental implementations, which can\n"
+ "> exist when the ratified version is implemented in theory (so there\342\200\231s no\n"
+ "> compatibility concern based on ISA changes) but isn\342\200\231t deemed\n"
  "> production-ready (e.g. potential ABI instability in the case of\n"
  "> something like V).\n"
  "\n"
@@ -69,14 +81,16 @@
  "While the vector extension might be okay in that regard, another\n"
  "extension well not be okay to use the \"unversioned\" experimental version\n"
  "of. Sounds like removing that option and picking the version of clang\n"
- "that adds the actual implementation is a better approach, at least IMO.\n"
+ that adds the actual implementation is a better approach, at least IMO.
+ "\01:2\0"
+ "fn\0signature.asc\0"
+ "b\0"
+ "-----BEGIN PGP SIGNATURE-----\n"
  "\n"
- "-------------- next part --------------\n"
- "A non-text attachment was scrubbed...\n"
- "Name: signature.asc\n"
- "Type: application/pgp-signature\n"
- "Size: 228 bytes\n"
- "Desc: not available\n"
- URL: <http://lists.infradead.org/pipermail/kvm-riscv/attachments/20230125/a31ba3da/attachment-0001.sig>
+ "iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCY9GsAAAKCRB4tDGHoIJi\n"
+ "0hqFAQC48XA84lz48uhvAtpzLEHeMOU2tUpSJ8GlckABIXQCJwEA3wPARCef7sAh\n"
+ "co6sjKqf4Skq3blkPVYO104tRYo0AAc=\n"
+ "=bxFQ\n"
+ "-----END PGP SIGNATURE-----\n"
 
-8f8c57fac0380acc8019016cf85a53698c4f0bd76385746e8c5e70ebf39d5593
+59bce6f1e1c9b1e567b837f109f71521b5f048f595b598222197dd83b85a807b

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.