)]}'
{
  "commit": "e1fef9e2ce4272b720ecb1ce696a72aaddbb7585",
  "tree": "7f0db2e1ff9ef4fac656f2fa0a89c3758cb4bb9e",
  "parents": [
    "8b092be9fd6a2cd84c437128e9b0d85e364efcfb"
  ],
  "author": {
    "name": "Geert Uytterhoeven",
    "email": "geert+renesas@glider.be",
    "time": "Fri Dec 04 16:33:53 2015 +0100"
  },
  "committer": {
    "name": "Linus Walleij",
    "email": "linus.walleij@linaro.org",
    "time": "Fri Dec 11 10:11:40 2015 +0100"
  },
  "message": "gpio: rcar: Improve clock error handling and reporting\n\nIf the Renesas R-Car GPIO driver cannot find a functional clock, it\nprints a warning, .e.g.\n\n\tgpio_rcar ffc40000.gpio: unable to get clock\n\nand continues, as the clock is optional, depending on the SoC type.\nThis warning may confuse users.\n\nTo fix this, add a flag to indicate that the clock is mandatory or\noptional:\n  - If the clock is mandatory (on R-Car Gen2 and Gen3), a missing clock\n    is now treated as a fatal error,\n  - If the clock is optional (on R-Car Gen1), the warning is no longer\n    printed.\n\nSuggested-by: Magnus Damm \u003cmagnus.damm@gmail.com\u003e\nSigned-off-by: Geert Uytterhoeven \u003cgeert+renesas@glider.be\u003e\nAcked-by: Simon Horman \u003chorms+renesas@verge.net.au\u003e\nSigned-off-by: Linus Walleij \u003clinus.walleij@linaro.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1ed52fc026cb4dd25d70efac28a303c2b4bee306",
      "old_mode": 33188,
      "old_path": "drivers/gpio/gpio-rcar.c",
      "new_id": "624a435e69889d7efede78f6f8a5df5b2597507e",
      "new_mode": 33188,
      "new_path": "drivers/gpio/gpio-rcar.c"
    }
  ]
}