Hi Peter,
Peter Verschoor wrote:
I applied the patch to my
debian 3.1 kernel tree, built and installed a new kernel and it came
up just fine. Still testing to check everything else.
Thanks again for this. Now the fix has been applied in Debian
Peter Verschoor wrote:
Looking through the dmesg output I see where it left the IRQ at
51. (It gets rerouted to 19 in the 3.1.1 kernel) Since the bug was
triggered by the new code added to drivers/acpi/pci_irq.c, which in
not present in the 3.0.x tree, it isn't too surprising that
reassign 650119 src:linux-2.6 3.1.1-1
severity 650119 important
# 6225da481597 (cciss: Add IRQF_SHARED back in for the non-MSI(X)
# interrupt handler, 2011-11-28), which is part of Jens Axboe's
# block/for-next tree.
tags 650119 = patch upstream
# theoretically
found 650119
On Thu, Dec 15, 2011 at 03:58:43PM -0600, Jonathan Nieder wrote:
reassign 650119 src:linux-2.6 3.1.1-1
severity 650119 important
# 6225da481597 (cciss: Add IRQF_SHARED back in for the non-MSI(X)
# interrupt handler, 2011-11-28), which is part of Jens Axboe's
# block/for-next tree.
tags
On Thu, Dec 15, 2011 at 03:58:43PM -0600, Jonathan Nieder wrote:
reassign 650119 src:linux-2.6 3.1.1-1
severity 650119 important
# 6225da481597 (cciss: Add IRQF_SHARED back in for the non-MSI(X)
# interrupt handler, 2011-11-28), which is part of Jens Axboe's
# block/for-next tree.
tags
Greg KH wrote:
On Thu, Dec 15, 2011 at 03:58:43PM -0600, Jonathan Nieder wrote:
Stephen, once it hits mainline, would 6225da481597 be a candidate for
the current-maintained stable trees = 2.6.36, or does it have any
prerequisites or followups that should go with it?
formletter
This is not
On Thu, Dec 15, 2011 at 05:13:52PM -0600, Jonathan Nieder wrote:
Greg KH wrote:
On Thu, Dec 15, 2011 at 03:58:43PM -0600, Jonathan Nieder wrote:
Stephen, once it hits mainline, would 6225da481597 be a candidate for
the current-maintained stable trees = 2.6.36, or does it have any
Greg KH wrote:
On Thu, Dec 15, 2011 at 05:13:52PM -0600, Jonathan Nieder wrote:
I thought step 1 in the right way was for the patch to hit mainline. :)
Yes it is, and until that happens, why are you emailing
sta...@vger.kernel.org about this? There's nothing I can do about it at
this point
8 matches
Mail list logo