All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20140322062432.GB5938@dragon>

diff --git a/a/1.txt b/N1/1.txt
index f804494..0268678 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -9,14 +9,14 @@ On Tue, Mar 18, 2014 at 02:15:19PM -0600, Jason Gunthorpe wrote:
 > It is documented in the 'PCI Bus Binding to Open Firware'
 > publication from IEEE.
 > 
-> > >> +             pcie at 0,0 {
+> > >> +             pcie@0,0 {
 > > >> +                     /* 01:00.0 PCIe switch */
 > > >> +                     #address-cells = <3>;
 > > >> +                     #size-cells = <2>;
 > > >> +                     device_type = "pci";
 > > >> +                     reg = <0x0 0 0 0 0>;
 > > >> +
-> > >> +                     pcie at 8,0 {
+> > >> +                     pcie@8,0 {
 > > >
 > > > What's the naming schema for all these pcie nodes?  Generally, we should
 > > > have the numbers encoded in the node name coming from the address cells
@@ -32,3 +32,8 @@ Ok, thanks for the info.  I missed the fact the pointer to the spec has
 been there in Documentation/devicetree/bindings/pci/pci.txt.
 
 Shawn
+
+--
+To unsubscribe from this list: send the line "unsubscribe devicetree" in
+the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
+More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff --git a/a/content_digest b/N1/content_digest
index 2f90a38..87bf620 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -2,10 +2,15 @@
  "ref\020140314132805.GD813@S2101-09.ap.freescale.net\0"
  "ref\0CAJ+vNU2Av-n1-efbFbXNvO4SmoobL_WpQKApFRS1Zjy0egLLzw@mail.gmail.com\0"
  "ref\020140318201519.GA8637@obsidianresearch.com\0"
- "From\0shawn.guo@freescale.com (Shawn Guo)\0"
- "Subject\0[PATCH] ARM: dts: ventana: fix eth1 pci dev node\0"
+ "ref\020140318201519.GA8637-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org\0"
+ "From\0Shawn Guo <shawn.guo-KZfg59tc24xl57MIdRCFDg@public.gmane.org>\0"
+ "Subject\0Re: [PATCH] ARM: dts: ventana: fix eth1 pci dev node\0"
  "Date\0Sat, 22 Mar 2014 14:25:17 +0800\0"
- "To\0linux-arm-kernel@lists.infradead.org\0"
+ "To\0Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>\0"
+ "Cc\0Tim Harvey <tharvey-UMMOYl/HMS+akBO8gow8eQ@public.gmane.org>"
+  devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
+  Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
+ " linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org <linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>\0"
  "\00:1\0"
  "b\0"
  "On Tue, Mar 18, 2014 at 02:15:19PM -0600, Jason Gunthorpe wrote:\n"
@@ -19,14 +24,14 @@
  "> It is documented in the 'PCI Bus Binding to Open Firware'\n"
  "> publication from IEEE.\n"
  "> \n"
- "> > >> +             pcie at 0,0 {\n"
+ "> > >> +             pcie@0,0 {\n"
  "> > >> +                     /* 01:00.0 PCIe switch */\n"
  "> > >> +                     #address-cells = <3>;\n"
  "> > >> +                     #size-cells = <2>;\n"
  "> > >> +                     device_type = \"pci\";\n"
  "> > >> +                     reg = <0x0 0 0 0 0>;\n"
  "> > >> +\n"
- "> > >> +                     pcie at 8,0 {\n"
+ "> > >> +                     pcie@8,0 {\n"
  "> > >\n"
  "> > > What's the naming schema for all these pcie nodes?  Generally, we should\n"
  "> > > have the numbers encoded in the node name coming from the address cells\n"
@@ -41,6 +46,11 @@
  "Ok, thanks for the info.  I missed the fact the pointer to the spec has\n"
  "been there in Documentation/devicetree/bindings/pci/pci.txt.\n"
  "\n"
- Shawn
+ "Shawn\n"
+ "\n"
+ "--\n"
+ "To unsubscribe from this list: send the line \"unsubscribe devicetree\" in\n"
+ "the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\n"
+ More majordomo info at  http://vger.kernel.org/majordomo-info.html
 
-01dbbe1ba3b85672042fb4f742895e099a225e3b27d3281fdda9292b9aa09b57
+c4e04e6cf20f7e624629642ef8d77b3e64bb37b975d0509a743f929689bd2d7a

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.