All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <1517892624.2312.167.camel@kernel.crashing.org>

diff --git a/a/1.txt b/N1/1.txt
index 42b0339..83cc419 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -73,3 +73,9 @@ interrupt-parent & interrupts in those root port nodes.
 
 Cheers,
 Ben.
+
+
+_______________________________________________
+linux-arm-kernel mailing list
+linux-arm-kernel@lists.infradead.org
+http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
diff --git a/a/content_digest b/N1/content_digest
index 040a956..d6d1147 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -95,6 +95,12 @@
  "interrupt-parent & interrupts in those root port nodes.\n"
  "\n"
  "Cheers,\n"
- Ben.
+ "Ben.\n"
+ "\n"
+ "\n"
+ "_______________________________________________\n"
+ "linux-arm-kernel mailing list\n"
+ "linux-arm-kernel@lists.infradead.org\n"
+ http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
 
-b56622d2fc249a360ff69c3e8e276017934a93dd21b598c3bdc0e6920388b731
+055a8b38ec84e4d31758612946725529a9d05337cf9091f3ccca690f09baafc9

diff --git a/a/1.txt b/N2/1.txt
index 42b0339..19243d1 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -18,7 +18,7 @@ On Tue, 2018-02-06 at 12:31 +0800, Ryder Lee wrote:
 > > > 				 0x0800 0 0 3 ...>,
 > > > 				 0x0800 0 0 4 ...>;
 > > > 		...
-> > > 		pcie@1,0 {
+> > > 		pcie at 1,0 {
 > > > 			reg = <0x0800 0 0 0 0>;
 > > > 			...
 > > > 		};
@@ -40,8 +40,8 @@ On Tue, 2018-02-06 at 12:31 +0800, Ryder Lee wrote:
 > > basically) and how does that map to your representation ?
 > 
 > # lspci
-> 00:00.0 Class 0604: 14c3:0801 //1st slot - pcie@0,0
-> 00:01.0 Class 0604: 14c3:0801 //2nd slot - pcie@1,0
+> 00:00.0 Class 0604: 14c3:0801 //1st slot - pcie at 0,0
+> 00:01.0 Class 0604: 14c3:0801 //2nd slot - pcie at 1,0
 > 
 > 01:00.0 Class 0280: 14c3:7603 //A device which is connected to 1st slot
 > 02:00.0 Class 0200: 8086:1521 //A 4 func device which is connected to
@@ -58,7 +58,7 @@ However, that map only represents the INTA..D lines going to the root
 ports, not how these get mapped to children of the root ports.
 
 of_irq_parse_pci() will implement standard swizzling if you don't have
-nodes for your devices at all. If you do, however, the code assumes
+nodes for your devices@all. If you do, however, the code assumes
 you have a correct and complete interrupt tree in the device-tree.
 
 That means that you need in each "p2p bridge", including your root
diff --git a/a/content_digest b/N2/content_digest
index 040a956..5f85577 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -5,20 +5,10 @@
  "ref\01517884738.16010.27.camel@mtkswgap22\0"
  "ref\01517889903.2312.151.camel@kernel.crashing.org\0"
  "ref\01517891471.20869.6.camel@mtkswgap22\0"
- "From\0Benjamin Herrenschmidt <benh@kernel.crashing.org>\0"
- "Subject\0Re: [PATCH 1/2] of_pci_irq: add a check to fallback to standard device tree parsing\0"
+ "From\0benh@kernel.crashing.org (Benjamin Herrenschmidt)\0"
+ "Subject\0[PATCH 1/2] of_pci_irq: add a check to fallback to standard device tree parsing\0"
  "Date\0Tue, 06 Feb 2018 15:50:24 +1100\0"
- "To\0Ryder Lee <ryder.lee@mediatek.com>\0"
- "Cc\0open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS <devicetree@vger.kernel.org>"
-  Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
-  Arnd Bergmann <arnd@arndb.de>
-  linux-pci@vger.kernel.org
-  linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>
-  Rob Herring <robh+dt@kernel.org>
-  linux-mediatek@lists.infradead.org
-  Bjorn Helgaas <bhelgaas@google.com>
-  Frank Rowand <frowand.list@gmail.com>
- " moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE <linux-arm-kernel@lists.infradead.org>\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "On Tue, 2018-02-06 at 12:31 +0800, Ryder Lee wrote:\n"
@@ -41,7 +31,7 @@
  "> > > \t\t\t\t 0x0800 0 0 3 ...>,\n"
  "> > > \t\t\t\t 0x0800 0 0 4 ...>;\n"
  "> > > \t\t...\n"
- "> > > \t\tpcie@1,0 {\n"
+ "> > > \t\tpcie at 1,0 {\n"
  "> > > \t\t\treg = <0x0800 0 0 0 0>;\n"
  "> > > \t\t\t...\n"
  "> > > \t\t};\n"
@@ -63,8 +53,8 @@
  "> > basically) and how does that map to your representation ?\n"
  "> \n"
  "> # lspci\n"
- "> 00:00.0 Class 0604: 14c3:0801 //1st slot - pcie@0,0\n"
- "> 00:01.0 Class 0604: 14c3:0801 //2nd slot - pcie@1,0\n"
+ "> 00:00.0 Class 0604: 14c3:0801 //1st slot - pcie at 0,0\n"
+ "> 00:01.0 Class 0604: 14c3:0801 //2nd slot - pcie at 1,0\n"
  "> \n"
  "> 01:00.0 Class 0280: 14c3:7603 //A device which is connected to 1st slot\n"
  "> 02:00.0 Class 0200: 8086:1521 //A 4 func device which is connected to\n"
@@ -81,7 +71,7 @@
  "ports, not how these get mapped to children of the root ports.\n"
  "\n"
  "of_irq_parse_pci() will implement standard swizzling if you don't have\n"
- "nodes for your devices at all. If you do, however, the code assumes\n"
+ "nodes for your devices@all. If you do, however, the code assumes\n"
  "you have a correct and complete interrupt tree in the device-tree.\n"
  "\n"
  "That means that you need in each \"p2p bridge\", including your root\n"
@@ -97,4 +87,4 @@
  "Cheers,\n"
  Ben.
 
-b56622d2fc249a360ff69c3e8e276017934a93dd21b598c3bdc0e6920388b731
+bc33c4a5923e6462db6869a94548a25492aa10e51dd445fa01ca20eea32a6038

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.