)]}'
{
  "commit": "a03a202e95fdaa3ff52ccfc2594ec531e5917816",
  "tree": "872f242e564673c80be970bad141075d65b103da",
  "parents": [
    "e2f5e5a71dfe6bf155590de0fdd6d748ac79bf76"
  ],
  "author": {
    "name": "Guennadi Liakhovetski",
    "email": "g.liakhovetski@gmx.de",
    "time": "Mon Jun 20 17:02:47 2011 +0200"
  },
  "committer": {
    "name": "Vinod Koul",
    "email": "vinod.koul@intel.com",
    "time": "Fri Jun 24 16:13:16 2011 +0530"
  },
  "message": "dmaengine: failure to get a specific DMA channel is not critical\n\nThere exist systems with multiple DMA controllers with different\ncapabilities. For example, on some sh-mobile / rmobile systems there are\nDMA controllers, whose channels can be configured to be used with\nSD- and MMC-host controllers, serial ports etc. Besides there are also\nDMA controllers, that can only be used for one special function, e.g.,\nfor USB. In such cases the DMA client filter function can just choose\nto specify to the DMA driver, which channel it needs. Then the\n.device_alloc_chan_resources() method of the DMA driver will check,\nwhether it can provide that dunction. If not, it will fail and the loop\nin __dma_request_channel() will continue to the next DMA device, until\nit finds a suitable one. This works fine with just one minor glitch:\nthe kernel logs error messages like\n\ndmaengine: failed to get \u003cchannel name\u003e: (-\u003cerror code\u003e)\n\nafter each such non-critical failure. This patch lowers priority of\nthis message to the debug level.\n\nReported-by: Kuninori Morimoto \u003ckuninori.morimoto.gx@renesas.com\u003e\nSigned-off-by: Guennadi Liakhovetski \u003cg.liakhovetski@gmx.de\u003e\nTested-by: Kuninori Morimoto \u003ckuninori.morimoto.gx@renesas.com\u003e\nTested-by: Magnus Damm \u003cdamm@opensource.se\u003e\nSigned-off-by: Vinod Koul \u003cvinod.koul@intel.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8bcb15fb959d1e3de64e79a5e90300c105d62ad3",
      "old_mode": 33188,
      "old_path": "drivers/dma/dmaengine.c",
      "new_id": "f7f21a5de3e103111fc7645f56e1224abdf5f46d",
      "new_mode": 33188,
      "new_path": "drivers/dma/dmaengine.c"
    }
  ]
}