)]}'
{
  "commit": "691cd0c2ee2d4d6dff652627fca1b2d4f1377d58",
  "tree": "a2675498494e68634f8aaa294a65a27d1c7ccc56",
  "parents": [
    "4516a618a76eae6eb1b37259ad49f39b7b7f33d8"
  ],
  "author": {
    "name": "Andreas Block",
    "email": "andreas.block@esd-electronics.com",
    "time": "Mon Feb 05 16:36:07 2007 -0800"
  },
  "committer": {
    "name": "Greg Kroah-Hartman",
    "email": "gregkh@suse.de",
    "time": "Fri Feb 16 15:30:10 2007 -0800"
  },
  "message": "PCI: PCI devices get assigned redundant IRQs\n\nI\u0027m currently working on a port to a CPCI board with a MPC5200.  When\ntesting the PCI interrupt routing, I discovered the following: Even devices\nwhich don\u0027t use interrupts (-\u003e PCI Spec.: Interrupt Pin Register is zero),\nget an interrupt assigned (this is at least true for most of the\nPPC-targets I looked at).\n\nThe cause is pretty obvious in drivers/pci/setup-irq.c.  I guess at least\nin an ideal world with correctly designed hardware, the code should rather\nlook as in the patch below.\n\nOf course it doesn\u0027t hurt anybody to have an unuseable IRQ assigned to a\nPCI-to-PCI-bridge (or something alike), but to me it seems a bit strange. \nPlease correct me, if I\u0027m mislead.\n\nThe patch below is tested on the above mentioned CPCI-MPC5200 board and is\ncompiler tested with the latest git-repository kernel on x86.\n\nCc: \"Eric W. Biederman\" \u003cebiederm@xmission.com\u003e\nCc: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: Ingo Molnar \u003cmingo@elte.hu\u003e\nCc: Linus Torvalds \u003ctorvalds@osdl.org\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a251289c9958e846ebc50d45254ec2bea6b14cf5",
      "old_mode": 33188,
      "old_path": "drivers/pci/setup-irq.c",
      "new_id": "568f1877315c5532d39052e4e615f1304a48cb93",
      "new_mode": 33188,
      "new_path": "drivers/pci/setup-irq.c"
    }
  ]
}