)]}'
{
  "commit": "f0d44ae310bc8eb0b6694e257015d8b24e1a357c",
  "tree": "5687fbe1f5c7e2eeaa55de384b58f0764fae6ab8",
  "parents": [
    "f17f5c91ae3bfeb5cfc37fa132a5fdfceb8927be"
  ],
  "author": {
    "name": "Anton Vorontsov",
    "email": "avorontsov@ru.mvista.com",
    "time": "Wed Jan 14 14:38:02 2009 -0800"
  },
  "committer": {
    "name": "David S. Miller",
    "email": "davem@davemloft.net",
    "time": "Wed Jan 14 14:38:02 2009 -0800"
  },
  "message": "phylib: Fix Freescale TBI PHY detection\n\nFreescale on-chip TBI PHYs reports PHY ID as 0x0, but as of\n\ncommit 3ee82383f0098a2e13acc8cf1be8e47512f41e5a\nAuthor: Giulio Benetti \u003cgiulio.benetti@micronovasrl.com\u003e\nDate:   Thu Nov 13 21:53:13 2008 +0000\n\n    phy: fix phy address bug\n\n    PHYID returns 0xffff and not 0xffffffff when not found and in some\n    case(at91sam9263) 0x0. Maybe this patch could be useful.\n\nphy_device.c treats PHY ID \u003d\u003d 0x0 as bogus IDs, and that results in\ngianfar driver failure to see the TBI PHYs. This code snippet triggers:\n\n\tif (!priv-\u003etbiphy) {\n\t\tprintk(KERN_WARNING \"SGMII mode requires that the device \"\n\t\t\t\t\"tree specify a tbi-handle\\n\");\n\t\treturn;\n\t}\n\nAlthough tbi-handle is specified in the device tree.\n\nBtw, technically PHY ID \u003d\u003d 0x0 is a valid ID (if we ever see a PHY\nmanufactured by Xerox :-).\n\nSigned-off-by: Anton Vorontsov \u003cavorontsov@ru.mvista.com\u003e\nAcked-by: Andy Fleming \u003cafleming@freescale.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e35460165bf76709211ffa16f969a3b1fb07dbe8",
      "old_mode": 33188,
      "old_path": "drivers/net/phy/phy_device.c",
      "new_id": "0a06e4fd37d9b16e37a9e54e901cd659d7044163",
      "new_mode": 33188,
      "new_path": "drivers/net/phy/phy_device.c"
    }
  ]
}