All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <55FC2387.9080304@list.ru>

diff --git a/a/1.txt b/N1/1.txt
index 8bbc75d..789429d 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,10 +1,10 @@
-18.09.2015 16:57, Russell King - ARM Linux ?????:
+18.09.2015 16:57, Russell King - ARM Linux пишет:
 > On Fri, Sep 18, 2015 at 04:43:59PM +0300, Stas Sergeev wrote:
->> 18.09.2015 16:12, Russell King - ARM Linux ?????:
+>> 18.09.2015 16:12, Russell King - ARM Linux пишет:
 >>> On Fri, Sep 18, 2015 at 03:43:54PM +0300, Stas Sergeev wrote:
->>>> 18.09.2015 15:13, Russell King - ARM Linux ?????:
+>>>> 18.09.2015 15:13, Russell King - ARM Linux пишет:
 >>>>> On Fri, Sep 18, 2015 at 02:29:34PM +0300, Stas Sergeev wrote:
->>>>>> 18.09.2015 02:14, Russell King - ARM Linux ?????:
+>>>>>> 18.09.2015 02:14, Russell King - ARM Linux пишет:
 >>>>>>>  _But_ using the in-band status
 >>>>>>>    property fundamentally requires this for mvneta to behave correctly:
 >>>>>>>
@@ -116,7 +116,7 @@ Then it should have use_inband_status==false, right?
 >>> Consider what the effect is if you have a MDIO phy at address 0 on eth0
 >>> which has in-band-status enabled.
 >> So as I understand, you have MDIO phy with DT looking like this:
->> ethernet at 70000 {
+>> ethernet@70000 {
 >>   status = "okay";
 >>   phy-mode = "sgmii";
 >>   managed = "in-band-status";
@@ -127,19 +127,19 @@ Then it should have use_inband_status==false, right?
 >> non-MDIO phy. What I don't see is how do they get the same addr
 >> on the same bus, could you please clarify that a bit?
 > 
-> 		mdio at 72004 {
-> 			phy_dedicated: ethernet-phy at 0 {
+> 		mdio@72004 {
+> 			phy_dedicated: ethernet-phy@0 {
 > 				reg = <0>;
 > 			};
 > 		};
 > 
-> 		eth1: ethernet at 30000 {
+> 		eth1: ethernet@30000 {
 > 			phy = <&phy_dedicated>;
 > 			phy-mode = "sgmii";
 > 			managed = "in-band-status";
 > 		};
 > 
-> 		eth0: ethernet at 70000 {
+> 		eth0: ethernet@70000 {
 > 			phy-mode = "sgmii";
 > 			fixed-link {
 > 				speed = 1000;
diff --git a/a/content_digest b/N1/content_digest
index 920fdcc..ccb80ca 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -9,19 +9,23 @@
  "ref\020150918131257.GF21084@n2100.arm.linux.org.uk\0"
  "ref\055FC151F.6040708@list.ru\0"
  "ref\020150918135746.GG21084@n2100.arm.linux.org.uk\0"
- "From\0stsp@list.ru (Stas Sergeev)\0"
- "Subject\0mvneta: SGMII fixed-link not so fixed\0"
+ "From\0Stas Sergeev <stsp@list.ru>\0"
+ "Subject\0Re: mvneta: SGMII fixed-link not so fixed\0"
  "Date\0Fri, 18 Sep 2015 17:45:27 +0300\0"
- "To\0linux-arm-kernel@lists.infradead.org\0"
+ "To\0Russell King - ARM Linux <linux@arm.linux.org.uk>\0"
+ "Cc\0David Miller <davem@davemloft.net>"
+  andrew@lunn.ch
+  linux-arm-kernel@lists.infradead.org
+ " netdev@vger.kernel.org\0"
  "\00:1\0"
  "b\0"
- "18.09.2015 16:57, Russell King - ARM Linux ?????:\n"
+ "18.09.2015 16:57, Russell King - ARM Linux \320\277\320\270\321\210\320\265\321\202:\n"
  "> On Fri, Sep 18, 2015 at 04:43:59PM +0300, Stas Sergeev wrote:\n"
- ">> 18.09.2015 16:12, Russell King - ARM Linux ?????:\n"
+ ">> 18.09.2015 16:12, Russell King - ARM Linux \320\277\320\270\321\210\320\265\321\202:\n"
  ">>> On Fri, Sep 18, 2015 at 03:43:54PM +0300, Stas Sergeev wrote:\n"
- ">>>> 18.09.2015 15:13, Russell King - ARM Linux ?????:\n"
+ ">>>> 18.09.2015 15:13, Russell King - ARM Linux \320\277\320\270\321\210\320\265\321\202:\n"
  ">>>>> On Fri, Sep 18, 2015 at 02:29:34PM +0300, Stas Sergeev wrote:\n"
- ">>>>>> 18.09.2015 02:14, Russell King - ARM Linux ?????:\n"
+ ">>>>>> 18.09.2015 02:14, Russell King - ARM Linux \320\277\320\270\321\210\320\265\321\202:\n"
  ">>>>>>>  _But_ using the in-band status\n"
  ">>>>>>>    property fundamentally requires this for mvneta to behave correctly:\n"
  ">>>>>>>\n"
@@ -133,7 +137,7 @@
  ">>> Consider what the effect is if you have a MDIO phy at address 0 on eth0\n"
  ">>> which has in-band-status enabled.\n"
  ">> So as I understand, you have MDIO phy with DT looking like this:\n"
- ">> ethernet at 70000 {\n"
+ ">> ethernet@70000 {\n"
  ">>   status = \"okay\";\n"
  ">>   phy-mode = \"sgmii\";\n"
  ">>   managed = \"in-band-status\";\n"
@@ -144,19 +148,19 @@
  ">> non-MDIO phy. What I don't see is how do they get the same addr\n"
  ">> on the same bus, could you please clarify that a bit?\n"
  "> \n"
- "> \t\tmdio at 72004 {\n"
- "> \t\t\tphy_dedicated: ethernet-phy at 0 {\n"
+ "> \t\tmdio@72004 {\n"
+ "> \t\t\tphy_dedicated: ethernet-phy@0 {\n"
  "> \t\t\t\treg = <0>;\n"
  "> \t\t\t};\n"
  "> \t\t};\n"
  "> \n"
- "> \t\teth1: ethernet at 30000 {\n"
+ "> \t\teth1: ethernet@30000 {\n"
  "> \t\t\tphy = <&phy_dedicated>;\n"
  "> \t\t\tphy-mode = \"sgmii\";\n"
  "> \t\t\tmanaged = \"in-band-status\";\n"
  "> \t\t};\n"
  "> \n"
- "> \t\teth0: ethernet at 70000 {\n"
+ "> \t\teth0: ethernet@70000 {\n"
  "> \t\t\tphy-mode = \"sgmii\";\n"
  "> \t\t\tfixed-link {\n"
  "> \t\t\t\tspeed = 1000;\n"
@@ -177,4 +181,4 @@
  "Unfortunately this is not what needs to be explained.\n"
  I am confused about the setup path, not update path.
 
-170384c977b8495f41640f401311184c321197b2a0b2f2372e3d051c19db7e70
+06703103c3b59afe48a3f9cbb886e675b36d9300a56a79c0fd369a863fd46232

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.