All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <c2275ea94e0507a01b020ab66dfa824d8b1c2545.1592203650.git.mchehab+huawei@kernel.org>

diff --git a/a/1.txt b/N1/1.txt
index 39f6432..065eabf 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -31,16 +31,12 @@ index 8763866b11cf..349f44a29392 100644
 --- a/Documentation/crypto/asymmetric-keys.txt
 +++ b/Documentation/crypto/asymmetric-keys.rst
 @@ -1,8 +1,10 @@
--		=============================================
--		ASYMMETRIC / PUBLIC-KEY CRYPTOGRAPHY KEY TYPE
--		=============================================
-+.. SPDX-License-Identifier: GPL-2.0
+-		======================-		ASYMMETRIC / PUBLIC-KEY CRYPTOGRAPHY KEY TYPE
+-		======================+.. SPDX-License-Identifier: GPL-2.0
  
 -Contents:
-+=============================================
-+Asymmetric / Public-key Cryptography Key Type
-+=============================================
-+
++======================+Asymmetric / Public-key Cryptography Key Type
++======================+
 +.. Contents:
  
    - Overview.
@@ -49,20 +45,20 @@ index 8763866b11cf..349f44a29392 100644
    - Keyring link restrictions.
  
  
--========
+-====
 -OVERVIEW
 +Overview
- ========
+ ====
  
  The "asymmetric" key type is designed to be a container for the keys used in
 @@ -42,8 +43,7 @@ key, or it may interpret it as a reference to a key held somewhere else in the
  system (for example, a TPM).
  
  
--==================
+-=========
 -KEY IDENTIFICATION
 +Key Identification
- ==================
+ =========
  
  If a key is added with an empty name, the instantiation data parsers are given
 @@ -57,49 +57,48 @@ The asymmetric key type's match function can then perform a wider range of
@@ -98,11 +94,9 @@ index 8763866b11cf..349f44a29392 100644
  	1a39e171 I-----     1 perm 3f010000     0     0 asymmetric modsign.0: DSA 5acc2142 []
  
  
--=========================
--ACCESSING ASYMMETRIC KEYS
+-============-ACCESSING ASYMMETRIC KEYS
 +Accessing Asymmetric Keys
- =========================
- 
+ ============ 
  For general access to asymmetric keys from within the kernel, the following
 -inclusion is required:
 +inclusion is required::
@@ -160,11 +154,9 @@ index 8763866b11cf..349f44a29392 100644
  if the key argument is the wrong type or is incompletely set up.
  
  
--=======================
--ASYMMETRIC KEY SUBTYPES
+-===========-ASYMMETRIC KEY SUBTYPES
 +Asymmetric Key Subtypes
- =======================
- 
+ =========== 
  Asymmetric keys have a subtype that defines the set of operations that can be
 @@ -171,11 +169,11 @@ The subtype is selected by the key data parser and the parser must initialise
  the data required for it.  The asymmetric key retains a reference on the
@@ -220,10 +212,10 @@ index 8763866b11cf..349f44a29392 100644
       offloading to hardware.
  
 -
--==========================
+-=============
 -INSTANTIATION DATA PARSERS
 +Instantiation Data Parsers
- ==========================
+ =============
  
  The asymmetric key type doesn't generally want to store or to deal with a raw
 @@ -254,11 +250,11 @@ Examples of blob formats for which parsers could be implemented include:
@@ -271,11 +263,9 @@ index 8763866b11cf..349f44a29392 100644
  displaying in debugging messages.
  
  
--=========================
--KEYRING LINK RESTRICTIONS
+-============-KEYRING LINK RESTRICTIONS
 +Keyring Link Restrictions
- =========================
- 
+ ============ 
  Keyrings created from userspace using add_key can be configured to check the
 @@ -340,7 +335,7 @@ allowed to link.
  
diff --git a/a/content_digest b/N1/content_digest
index 1af17d1..fc79449 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -8,7 +8,7 @@
   "Subject\0[PATCH 03/22] docs: crypto: convert asymmetric-keys.txt to ReST\0"
 ]
 [
-  "Date\0Mon, 15 Jun 2020 08:50:08 +0200\0"
+  "Date\0Mon, 15 Jun 2020 06:50:08 +0000\0"
 ]
 [
   "To\0Linux Doc Mailing List <linux-doc\@vger.kernel.org>\0"
@@ -64,16 +64,12 @@
   "--- a/Documentation/crypto/asymmetric-keys.txt\n",
   "+++ b/Documentation/crypto/asymmetric-keys.rst\n",
   "\@\@ -1,8 +1,10 \@\@\n",
-  "-\t\t=============================================\n",
-  "-\t\tASYMMETRIC / PUBLIC-KEY CRYPTOGRAPHY KEY TYPE\n",
-  "-\t\t=============================================\n",
-  "+.. SPDX-License-Identifier: GPL-2.0\n",
+  "-\t\t======================-\t\tASYMMETRIC / PUBLIC-KEY CRYPTOGRAPHY KEY TYPE\n",
+  "-\t\t======================+.. SPDX-License-Identifier: GPL-2.0\n",
   " \n",
   "-Contents:\n",
-  "+=============================================\n",
-  "+Asymmetric / Public-key Cryptography Key Type\n",
-  "+=============================================\n",
-  "+\n",
+  "+======================+Asymmetric / Public-key Cryptography Key Type\n",
+  "+======================+\n",
   "+.. Contents:\n",
   " \n",
   "   - Overview.\n",
@@ -82,20 +78,20 @@
   "   - Keyring link restrictions.\n",
   " \n",
   " \n",
-  "-========\n",
+  "-====\n",
   "-OVERVIEW\n",
   "+Overview\n",
-  " ========\n",
+  " ====\n",
   " \n",
   " The \"asymmetric\" key type is designed to be a container for the keys used in\n",
   "\@\@ -42,8 +43,7 \@\@ key, or it may interpret it as a reference to a key held somewhere else in the\n",
   " system (for example, a TPM).\n",
   " \n",
   " \n",
-  "-==================\n",
+  "-=========\n",
   "-KEY IDENTIFICATION\n",
   "+Key Identification\n",
-  " ==================\n",
+  " =========\n",
   " \n",
   " If a key is added with an empty name, the instantiation data parsers are given\n",
   "\@\@ -57,49 +57,48 \@\@ The asymmetric key type's match function can then perform a wider range of\n",
@@ -131,11 +127,9 @@
   " \t1a39e171 I-----     1 perm 3f010000     0     0 asymmetric modsign.0: DSA 5acc2142 []\n",
   " \n",
   " \n",
-  "-=========================\n",
-  "-ACCESSING ASYMMETRIC KEYS\n",
+  "-============-ACCESSING ASYMMETRIC KEYS\n",
   "+Accessing Asymmetric Keys\n",
-  " =========================\n",
-  " \n",
+  " ============ \n",
   " For general access to asymmetric keys from within the kernel, the following\n",
   "-inclusion is required:\n",
   "+inclusion is required::\n",
@@ -193,11 +187,9 @@
   " if the key argument is the wrong type or is incompletely set up.\n",
   " \n",
   " \n",
-  "-=======================\n",
-  "-ASYMMETRIC KEY SUBTYPES\n",
+  "-===========-ASYMMETRIC KEY SUBTYPES\n",
   "+Asymmetric Key Subtypes\n",
-  " =======================\n",
-  " \n",
+  " =========== \n",
   " Asymmetric keys have a subtype that defines the set of operations that can be\n",
   "\@\@ -171,11 +169,11 \@\@ The subtype is selected by the key data parser and the parser must initialise\n",
   " the data required for it.  The asymmetric key retains a reference on the\n",
@@ -253,10 +245,10 @@
   "      offloading to hardware.\n",
   " \n",
   "-\n",
-  "-==========================\n",
+  "-=============\n",
   "-INSTANTIATION DATA PARSERS\n",
   "+Instantiation Data Parsers\n",
-  " ==========================\n",
+  " =============\n",
   " \n",
   " The asymmetric key type doesn't generally want to store or to deal with a raw\n",
   "\@\@ -254,11 +250,11 \@\@ Examples of blob formats for which parsers could be implemented include:\n",
@@ -304,11 +296,9 @@
   " displaying in debugging messages.\n",
   " \n",
   " \n",
-  "-=========================\n",
-  "-KEYRING LINK RESTRICTIONS\n",
+  "-============-KEYRING LINK RESTRICTIONS\n",
   "+Keyring Link Restrictions\n",
-  " =========================\n",
-  " \n",
+  " ============ \n",
   " Keyrings created from userspace using add_key can be configured to check the\n",
   "\@\@ -340,7 +335,7 \@\@ allowed to link.\n",
   " \n",
@@ -488,4 +478,4 @@
   "2.26.2"
 ]
 
-010746464f6da81b61b8949d9330c99fa882e0fa5419b3540eec51d5e8bfbb83
+cda325e62347b487e67beabc5d9151133ea80ca8f1d6c551a296ca6969e65ad8

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.