)]}'
{
  "commit": "ca8e99b32e3863c98ac958617cc157a00bf445b8",
  "tree": "2e8b5d9fc5577ef2c795c9cd4ca40ae21e508699",
  "parents": [
    "ee8a43a51c7681f19fe23b6b936e1d8094a8b7d1"
  ],
  "author": {
    "name": "Philip Rakity",
    "email": "prakity@marvell.com",
    "time": "Wed Jul 06 08:51:32 2011 -0700"
  },
  "committer": {
    "name": "Chris Ball",
    "email": "cjb@laptop.org",
    "time": "Wed Jul 20 17:21:16 2011 -0400"
  },
  "message": "mmc: core: Set non-default Drive Strength via platform hook\n\nNon default Drive Strength cannot be set automatically.  It is a function\nof the board design and only if there is a specific platform handler can\nit be set.  The platform handler needs to take into account the board\ndesign.  Pass to the platform code the necessary information.\n\nFor example:  The card and host controller may indicate they support HIGH\nand LOW drive strength.  There is no way to know what should be chosen\nwithout specific board knowledge.  Setting HIGH may lead to reflections\nand setting LOW may not suffice.  There is no mechanism (like ethernet\nduplex or speed pulses) to determine what should be done automatically.\n\nIf no platform handler is defined -- use the default value.\n\nSigned-off-by: Philip Rakity \u003cprakity@marvell.com\u003e\nReviewed-by: Arindam Nath \u003carindam.nath@amd.com\u003e\nSigned-off-by: Chris Ball \u003ccjb@laptop.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ff2774128aa93b1231538b1f5e014b0df987e7ca",
      "old_mode": 33188,
      "old_path": "drivers/mmc/core/sd.c",
      "new_id": "633975ff2bb395f6e2e883c2e7ce05fb51ed8df2",
      "new_mode": 33188,
      "new_path": "drivers/mmc/core/sd.c"
    },
    {
      "type": "modify",
      "old_id": "9f9a4c64cde7b42f719c45e7f118c7fbf688e5d2",
      "old_mode": 33188,
      "old_path": "include/linux/mmc/host.h",
      "new_id": "0f83858147a626c1a0bf463597e4f6ff82adfa3c",
      "new_mode": 33188,
      "new_path": "include/linux/mmc/host.h"
    }
  ]
}