)]}'
{
  "commit": "eb2dc35d99028b698cdedba4f5522bc43e576bd2",
  "tree": "eea807e548f06aa7f0cb74c8815d39529bef16a8",
  "parents": [
    "65841fd5132c3941cdf5df09e70df3ed28323212"
  ],
  "author": {
    "name": "françois romieu",
    "email": "romieu@fr.zoreil.com",
    "time": "Wed Jun 20 12:09:18 2012 +0000"
  },
  "committer": {
    "name": "David S. Miller",
    "email": "davem@davemloft.net",
    "time": "Fri Jun 22 21:48:32 2012 -0700"
  },
  "message": "r8169: RxConfig hack for the 8168evl.\n\nThe 8168evl (RTL_GIGA_MAC_VER_34) based Gigabyte GA-990FXA motherboards\nare very prone to NETDEV watchdog problems without this change. See\nhttps://bugzilla.kernel.org/show_bug.cgi?id\u003d42899 for instance.\n\nI don\u0027t know why it *works*. It\u0027s depressingly effective though.\n\nFor the record:\n- the problem may go along IOMMU (AMD-Vi) errors but it really looks\n  like a red herring.\n- the patch sets the RX_MULTI_EN bit. If the 8168c doc is any guide,\n  the chipset now fetches several Rx descriptors at a time.\n- long ago the driver ignored the RX_MULTI_EN bit.\n  e542a2269f232d61270ceddd42b73a4348dee2bb changed the RxConfig\n  settings. Whatever the problem it\u0027s now labeled a regression.\n- Realtek\u0027s own driver can identify two different 8168evl devices\n  (CFG_METHOD_16 and CFG_METHOD_17) where the r8169 driver only\n  sees one. It sucks.\n\nSigned-off-by: Francois Romieu \u003cromieu@fr.zoreil.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "7260aa79466a06055c56ad37d1a97119f4399031",
      "old_mode": 33188,
      "old_path": "drivers/net/ethernet/realtek/r8169.c",
      "new_id": "d7a04e0911012649f48b85bbf5521ee2dc05ddbe",
      "new_mode": 33188,
      "new_path": "drivers/net/ethernet/realtek/r8169.c"
    }
  ]
}