All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <52802E34.5020209@gmail.com>

diff --git a/a/1.txt b/N1/1.txt
index ab39476..7429fc0 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,10 +1,10 @@
 On 11/11/2013 01:32 AM, Arnaud Ebalard wrote:
-> Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> writes:
+> Sebastian Hesselbarth <sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
 >>>>> +				status = "okay";
 >>>>> +			};
 >>>>> +
 >>>>> +			mdio {
->>>>> +				phy0: ethernet-phy at 0 {
+>>>>> +				phy0: ethernet-phy@0 {
 >>>>> +					reg = <0>;
 >>>>
 >>>> Can you evaluate PHYs compatible from u-boot or post vendor:prodid
@@ -21,7 +21,7 @@ On 11/11/2013 01:32 AM, Arnaud Ebalard wrote:
 >
 > For the records, another solution is to look under /sys/:
 >
-> root at thin:/sys/bus/mdio_bus/drivers# find -name '*mdio*'
+> root@thin:/sys/bus/mdio_bus/drivers# find -name '*mdio*'
 > ./Marvell 88E1318S/d0072004.mdio-mi:00
 > ./Marvell 88E1318S/d0072004.mdio-mi:01
 
@@ -56,7 +56,7 @@ name. G762 datasheet might have a good name for it, like clock-crystal
 or something.
 
 > Can you confirm the following: g762_clk is a *label for the node*, which
-> is referenced via specific properties of g762 at xx nodes, so that they get
+> is referenced via specific properties of g762@xx nodes, so that they get
 > a clock frequency (a property of g762_clk). And fixedclk is *the name of
 > the node*. In that specific case, fixedclk is ok because it does not
 > collide w/ any existing node. But 'oscillator' is already defined in
@@ -86,3 +86,8 @@ different node label could be a hint for the latter though.
 Sorry for the extra work that comment caused.
 
 Sebastian
+
+--
+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 2219312..bc542bf 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -3,19 +3,34 @@
  "ref\087hablulxu.fsf@natisbad.org\0"
  "ref\0527ED9E5.80800@gmail.com\0"
  "ref\087fvr393ro.fsf@natisbad.org\0"
- "From\0sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)\0"
- "Subject\0[PATCH] ARM: mvebu: Add Netgear ReadyNAS 2120 board\0"
+ "ref\087fvr393ro.fsf-LkuqDEemtHBg9hUCZPvPmw@public.gmane.org\0"
+ "From\0Sebastian Hesselbarth <sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>\0"
+ "Subject\0Re: [PATCH] ARM: mvebu: Add Netgear ReadyNAS 2120 board\0"
  "Date\0Mon, 11 Nov 2013 02:09:08 +0100\0"
- "To\0linux-arm-kernel@lists.infradead.org\0"
+ "To\0Arnaud Ebalard <arno-LkuqDEemtHBg9hUCZPvPmw@public.gmane.org>\0"
+ "Cc\0Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>"
+  Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>
+  Gregory Clement <gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
+  Ezequiel Garcia <ezequiel.garcia-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
+  Thomas Petazzoni <thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
+  Russell King <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>
+  linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
+  Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>
+  Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>
+  Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>
+  Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
+  Ian Campbell <ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>
+  devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
+ " Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>\0"
  "\00:1\0"
  "b\0"
  "On 11/11/2013 01:32 AM, Arnaud Ebalard wrote:\n"
- "> Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> writes:\n"
+ "> Sebastian Hesselbarth <sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:\n"
  ">>>>> +\t\t\t\tstatus = \"okay\";\n"
  ">>>>> +\t\t\t};\n"
  ">>>>> +\n"
  ">>>>> +\t\t\tmdio {\n"
- ">>>>> +\t\t\t\tphy0: ethernet-phy at 0 {\n"
+ ">>>>> +\t\t\t\tphy0: ethernet-phy@0 {\n"
  ">>>>> +\t\t\t\t\treg = <0>;\n"
  ">>>>\n"
  ">>>> Can you evaluate PHYs compatible from u-boot or post vendor:prodid\n"
@@ -32,7 +47,7 @@
  ">\n"
  "> For the records, another solution is to look under /sys/:\n"
  ">\n"
- "> root at thin:/sys/bus/mdio_bus/drivers# find -name '*mdio*'\n"
+ "> root@thin:/sys/bus/mdio_bus/drivers# find -name '*mdio*'\n"
  "> ./Marvell 88E1318S/d0072004.mdio-mi:00\n"
  "> ./Marvell 88E1318S/d0072004.mdio-mi:01\n"
  "\n"
@@ -67,7 +82,7 @@
  "or something.\n"
  "\n"
  "> Can you confirm the following: g762_clk is a *label for the node*, which\n"
- "> is referenced via specific properties of g762 at xx nodes, so that they get\n"
+ "> is referenced via specific properties of g762@xx nodes, so that they get\n"
  "> a clock frequency (a property of g762_clk). And fixedclk is *the name of\n"
  "> the node*. In that specific case, fixedclk is ok because it does not\n"
  "> collide w/ any existing node. But 'oscillator' is already defined in\n"
@@ -96,6 +111,11 @@
  "\n"
  "Sorry for the extra work that comment caused.\n"
  "\n"
- Sebastian
+ "Sebastian\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
 
-e02f2907ccd1fb69b1d7cdc0b9bfd69055c3299bff6a944a90f9bd729e873bbb
+8db70afcad082193354103f3f3581c650bacefec8923f8e13bfde8bd54863f53

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.