)]}'
{
  "commit": "930bf7bfd7b754bf2d464c7574a02016104f2cb4",
  "tree": "21e050f0dc5e8dfa0df64093ab9f638a1d22fe0a",
  "parents": [
    "4317676a54fd89d971e3c1b16fc310fde3021812"
  ],
  "author": {
    "name": "Abhijeet Dharmapurikar",
    "email": "adharmap@codeaurora.org",
    "time": "Mon Jul 25 12:23:58 2011 -0700"
  },
  "committer": {
    "name": "Bryan Huntsman",
    "email": "bryanh@codeaurora.org",
    "time": "Mon Oct 03 10:27:09 2011 -0700"
  },
  "message": "mfd: pm8xxx-irq: workaround for lost interrupt issue\n\nAn issue of missing interrupt was observed while resuming the device.\nThe genirq framework calls __enable_irq on all the interrupts during\nresume.  This inturn calls unmask in the pm8xxx which caused the\npending status to drop for that interrupt. Later when the summary\nhandler is called, it does not see that interrupt pending and so its\nhandler is never called.\n\nThe pm8xxx irq module has a hardware bug where writing to the config\nbits clears the pending status of the interrupt.\n\nFix it by avoiding unmasking the interrupt again if it is already\nunmasked. This will prevent us from writing to the interrupt config\nstate, thus preventing dropping of the pending bit if set.\n\nCRs-Fixed: 297320\nSigned-off-by: Abhijeet Dharmapurikar \u003cadharmap@codeaurora.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c04d0d1bfe21d391dd60101b34b8c4345addf7a9",
      "old_mode": 33188,
      "old_path": "drivers/mfd/pm8xxx-irq.c",
      "new_id": "2ed39363d33ecef4cadcbe4ff0167acbe39ba9b0",
      "new_mode": 33188,
      "new_path": "drivers/mfd/pm8xxx-irq.c"
    }
  ]
}