All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20180912130131.2c6581d5@coco.lan>

diff --git a/a/1.txt b/N1/1.txt
index 01e26c6..b01bf48 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -42,7 +42,7 @@ using gpio-ir-recv and/or gpio-ir-tx drivers. Perhaps one possible
 practical usage would be to let the mainframe to send remote
 controller codes to adjust the air conditioning system ;-)
 
-From lirc driver's PoV, there's nothing that really prevents one to
+>From lirc driver's PoV, there's nothing that really prevents one to
 do that and use lirc API, and the driver is generic enough to work
 on any hardware platform.
 
diff --git a/a/content_digest b/N1/content_digest
index baa114f..8073349 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -29,7 +29,10 @@
   linux-usb@vger.kernel.org
   linux-fbdev@vger.kernel.org
   linuxppc-dev@lists.ozlabs.org
- " linux-btrfs@vger.ker\0"
+  linux-btrfs@vger.kernel.org
+  ceph-devel@vger.kernel.org
+  linux-wireless@vger.kernel.org
+ " netdev@vger.kernel.org\0"
  "\00:1\0"
  "b\0"
  "Em Wed, 12 Sep 2018 17:08:52 +0200\n"
@@ -76,7 +79,7 @@
  "practical usage would be to let the mainframe to send remote\n"
  "controller codes to adjust the air conditioning system ;-)\n"
  "\n"
- "From lirc driver's PoV, there's nothing that really prevents one to\n"
+ ">From lirc driver's PoV, there's nothing that really prevents one to\n"
  "do that and use lirc API, and the driver is generic enough to work\n"
  "on any hardware platform.\n"
  "\n"
@@ -88,4 +91,4 @@
  "Thanks,\n"
  Mauro
 
-6cbaf414764070f511c79a899f053f9d9ac972fcab3c073e42fce7e3e94c8426
+b4992d63137ee6b384f0b7988f1f1fe9bf6d7039f5e8826f55cd34f868f86203

diff --git a/a/content_digest b/N2/content_digest
index baa114f..f977f47 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -2,7 +2,7 @@
  "ref\020180912151134.436719-1-arnd@arndb.de\0"
  "From\0Mauro Carvalho Chehab <mchehab+samsung@kernel.org>\0"
  "Subject\0Re: [PATCH v2 05/17] compat_ioctl: move more drivers to generic_compat_ioctl_ptrarg\0"
- "Date\0Wed, 12 Sep 2018 13:01:31 -0300\0"
+ "Date\0Wed, 12 Sep 2018 16:01:31 +0000\0"
  "To\0Arnd Bergmann <arnd@arndb.de>\0"
  "Cc\0viro@zeniv.linux.org.uk"
   linux-fsdevel@vger.kernel.org
@@ -88,4 +88,4 @@
  "Thanks,\n"
  Mauro
 
-6cbaf414764070f511c79a899f053f9d9ac972fcab3c073e42fce7e3e94c8426
+c6f62e77dac4a3acbe46359c711b37beaf822985a294f2ddfe42a400f7cfccc3

diff --git a/a/content_digest b/N3/content_digest
index baa114f..9add68d 100644
--- a/a/content_digest
+++ b/N3/content_digest
@@ -29,7 +29,10 @@
   linux-usb@vger.kernel.org
   linux-fbdev@vger.kernel.org
   linuxppc-dev@lists.ozlabs.org
- " linux-btrfs@vger.ker\0"
+  linux-btrfs@vger.kernel.org
+  ceph-devel@vger.kernel.org
+  linux-wireless@vger.kernel.org
+ " netdev@vger.kernel.org\0"
  "\00:1\0"
  "b\0"
  "Em Wed, 12 Sep 2018 17:08:52 +0200\n"
@@ -88,4 +91,4 @@
  "Thanks,\n"
  Mauro
 
-6cbaf414764070f511c79a899f053f9d9ac972fcab3c073e42fce7e3e94c8426
+a9b588347f900785a2715d33c43c87c5a8918a6e2c3bb957afcc5956ee45c9fe

diff --git a/a/1.txt b/N4/1.txt
index 01e26c6..c783e73 100644
--- a/a/1.txt
+++ b/N4/1.txt
@@ -4,16 +4,16 @@ Arnd Bergmann <arnd@arndb.de> escreveu:
 > The .ioctl and .compat_ioctl file operations have the same prototype so
 > they can both point to the same function, which works great almost all
 > the time when all the commands are compatible.
-> 
+>=20
 > One exception is the s390 architecture, where a compat pointer is only
 > 31 bit wide, and converting it into a 64-bit pointer requires calling
 > compat_ptr(). Most drivers here will ever run in s390, but since we now
 > have a generic helper for it, it's easy enough to use it consistently.
-> 
+>=20
 > I double-checked all these drivers to ensure that all ioctl arguments
 > are used as pointers or are ignored, but are not interpreted as integer
 > values.
-> 
+>=20
 > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
 > ---
 
@@ -23,26 +23,26 @@ Arnd Bergmann <arnd@arndb.de> escreveu:
 > index f862f1b7f996..077209f414ed 100644
 > --- a/drivers/media/rc/lirc_dev.c
 > +++ b/drivers/media/rc/lirc_dev.c
-> @@ -730,9 +730,7 @@ static const struct file_operations lirc_fops = {
->  	.owner		= THIS_MODULE,
->  	.write		= ir_lirc_transmit_ir,
->  	.unlocked_ioctl	= ir_lirc_ioctl,
+> @@ -730,9 +730,7 @@ static const struct file_operations lirc_fops =3D {
+>  	.owner		=3D THIS_MODULE,
+>  	.write		=3D ir_lirc_transmit_ir,
+>  	.unlocked_ioctl	=3D ir_lirc_ioctl,
 > -#ifdef CONFIG_COMPAT
-> -	.compat_ioctl	= ir_lirc_ioctl,
+> -	.compat_ioctl	=3D ir_lirc_ioctl,
 > -#endif
-> +	.compat_ioctl	= generic_compat_ioctl_ptrarg,
->  	.read		= ir_lirc_read,
->  	.poll		= ir_lirc_poll,
->  	.open		= ir_lirc_open,
+> +	.compat_ioctl	=3D generic_compat_ioctl_ptrarg,
+>  	.read		=3D ir_lirc_read,
+>  	.poll		=3D ir_lirc_poll,
+>  	.open		=3D ir_lirc_open,
 
 Adding an infrared remote controller to a s390 mainframe sounds fun :-)
 
-I suspect that one could implement it on a s390 platform 
+I suspect that one could implement it on a s390 platform=20
 using gpio-ir-recv and/or gpio-ir-tx drivers. Perhaps one possible
 practical usage would be to let the mainframe to send remote
 controller codes to adjust the air conditioning system ;-)
 
-From lirc driver's PoV, there's nothing that really prevents one to
+=46rom lirc driver's PoV, there's nothing that really prevents one to
 do that and use lirc API, and the driver is generic enough to work
 on any hardware platform.
 
diff --git a/a/content_digest b/N4/content_digest
index baa114f..06eb6f8 100644
--- a/a/content_digest
+++ b/N4/content_digest
@@ -29,7 +29,10 @@
   linux-usb@vger.kernel.org
   linux-fbdev@vger.kernel.org
   linuxppc-dev@lists.ozlabs.org
- " linux-btrfs@vger.ker\0"
+  linux-btrfs@vger.kernel.org
+  ceph-devel@vger.kernel.org
+  linux-wireless@vger.kernel.org
+ " netdev@vger.kernel.org\0"
  "\00:1\0"
  "b\0"
  "Em Wed, 12 Sep 2018 17:08:52 +0200\n"
@@ -38,16 +41,16 @@
  "> The .ioctl and .compat_ioctl file operations have the same prototype so\n"
  "> they can both point to the same function, which works great almost all\n"
  "> the time when all the commands are compatible.\n"
- "> \n"
+ ">=20\n"
  "> One exception is the s390 architecture, where a compat pointer is only\n"
  "> 31 bit wide, and converting it into a 64-bit pointer requires calling\n"
  "> compat_ptr(). Most drivers here will ever run in s390, but since we now\n"
  "> have a generic helper for it, it's easy enough to use it consistently.\n"
- "> \n"
+ ">=20\n"
  "> I double-checked all these drivers to ensure that all ioctl arguments\n"
  "> are used as pointers or are ignored, but are not interpreted as integer\n"
  "> values.\n"
- "> \n"
+ ">=20\n"
  "> Signed-off-by: Arnd Bergmann <arnd@arndb.de>\n"
  "> ---\n"
  "\n"
@@ -57,26 +60,26 @@
  "> index f862f1b7f996..077209f414ed 100644\n"
  "> --- a/drivers/media/rc/lirc_dev.c\n"
  "> +++ b/drivers/media/rc/lirc_dev.c\n"
- "> @@ -730,9 +730,7 @@ static const struct file_operations lirc_fops = {\n"
- ">  \t.owner\t\t= THIS_MODULE,\n"
- ">  \t.write\t\t= ir_lirc_transmit_ir,\n"
- ">  \t.unlocked_ioctl\t= ir_lirc_ioctl,\n"
+ "> @@ -730,9 +730,7 @@ static const struct file_operations lirc_fops =3D {\n"
+ ">  \t.owner\t\t=3D THIS_MODULE,\n"
+ ">  \t.write\t\t=3D ir_lirc_transmit_ir,\n"
+ ">  \t.unlocked_ioctl\t=3D ir_lirc_ioctl,\n"
  "> -#ifdef CONFIG_COMPAT\n"
- "> -\t.compat_ioctl\t= ir_lirc_ioctl,\n"
+ "> -\t.compat_ioctl\t=3D ir_lirc_ioctl,\n"
  "> -#endif\n"
- "> +\t.compat_ioctl\t= generic_compat_ioctl_ptrarg,\n"
- ">  \t.read\t\t= ir_lirc_read,\n"
- ">  \t.poll\t\t= ir_lirc_poll,\n"
- ">  \t.open\t\t= ir_lirc_open,\n"
+ "> +\t.compat_ioctl\t=3D generic_compat_ioctl_ptrarg,\n"
+ ">  \t.read\t\t=3D ir_lirc_read,\n"
+ ">  \t.poll\t\t=3D ir_lirc_poll,\n"
+ ">  \t.open\t\t=3D ir_lirc_open,\n"
  "\n"
  "Adding an infrared remote controller to a s390 mainframe sounds fun :-)\n"
  "\n"
- "I suspect that one could implement it on a s390 platform \n"
+ "I suspect that one could implement it on a s390 platform=20\n"
  "using gpio-ir-recv and/or gpio-ir-tx drivers. Perhaps one possible\n"
  "practical usage would be to let the mainframe to send remote\n"
  "controller codes to adjust the air conditioning system ;-)\n"
  "\n"
- "From lirc driver's PoV, there's nothing that really prevents one to\n"
+ "=46rom lirc driver's PoV, there's nothing that really prevents one to\n"
  "do that and use lirc API, and the driver is generic enough to work\n"
  "on any hardware platform.\n"
  "\n"
@@ -88,4 +91,4 @@
  "Thanks,\n"
  Mauro
 
-6cbaf414764070f511c79a899f053f9d9ac972fcab3c073e42fce7e3e94c8426
+626393a0204837e6e3b3a2f23ee0456a11384671c52dbdc8bd63e263db02124a

diff --git a/a/content_digest b/N5/content_digest
index baa114f..5ec0c91 100644
--- a/a/content_digest
+++ b/N5/content_digest
@@ -1,7 +1,5 @@
- "ref\020180912150142.157913-1-arnd@arndb.de\0"
- "ref\020180912151134.436719-1-arnd@arndb.de\0"
  "From\0Mauro Carvalho Chehab <mchehab+samsung@kernel.org>\0"
- "Subject\0Re: [PATCH v2 05/17] compat_ioctl: move more drivers to generic_compat_ioctl_ptrarg\0"
+ "Subject\0[v2,05/17] compat_ioctl: move more drivers to generic_compat_ioctl_ptrarg\0"
  "Date\0Wed, 12 Sep 2018 13:01:31 -0300\0"
  "To\0Arnd Bergmann <arnd@arndb.de>\0"
  "Cc\0viro@zeniv.linux.org.uk"
@@ -29,7 +27,10 @@
   linux-usb@vger.kernel.org
   linux-fbdev@vger.kernel.org
   linuxppc-dev@lists.ozlabs.org
- " linux-btrfs@vger.ker\0"
+  linux-btrfs@vger.kernel.org
+  ceph-devel@vger.kernel.org
+  linux-wireless@vger.kernel.org
+ " netdev@vger.kernel.org\0"
  "\00:1\0"
  "b\0"
  "Em Wed, 12 Sep 2018 17:08:52 +0200\n"
@@ -88,4 +89,4 @@
  "Thanks,\n"
  Mauro
 
-6cbaf414764070f511c79a899f053f9d9ac972fcab3c073e42fce7e3e94c8426
+f8cc802ab93b58749b888b956a4df1424d4635c4f1ef9972dbcbd8db3201d672

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.