Re: [PATCH 2.4.19-bk8] arch/i386/kernel/pci-irq.c: Wrong message output

Mark F. Haigh wrote: Apologies. Patch now -p1-able. [Apologies yet again, now includes description] I'd submitted a patch earlier for this file, fixing a warning. When I looked at it further, I noticed it can output an incorrect warning message under certain circumstances. I've confirmed that

Re: [PATCH 2.4.19-bk8] arch/i386/kernel/pci-irq.c: Wrong message output

Mark F. Haigh wrote: --- arch/i386/kernel/pci-irq.c.orig 2005-02-07 19:55:23.852531544 -0800 +++ arch/i386/kernel/pci-irq.c 2005-02-07 20:13:38.835068896 -0800 Apologies. Patch now -p1-able. Mark F. Haigh [EMAIL PROTECTED] Signed-off-by: Mark F. Haigh <[EMAIL PROTECTED]> ---

[PATCH 2.4.19-bk8] arch/i386/kernel/pci-irq.c: Wrong message output

I'd submitted a patch earlier for this file, fixing a warning. When I looked at it further, I noticed it can output an incorrect warning message under certain circumstances. I've confirmed that this can and does happen in the wild: PCI: Enabling device :00:0a.0 ( -> 0001) PCI: No IRQ

[PATCH 2.4.19-bk8] arch/i386/kernel/pci-irq.c: Wrong message output

I'd submitted a patch earlier for this file, fixing a warning. When I looked at it further, I noticed it can output an incorrect warning message under certain circumstances. I've confirmed that this can and does happen in the wild: PCI: Enabling device :00:0a.0 ( - 0001) PCI: No IRQ

Re: [PATCH 2.4.19-bk8] arch/i386/kernel/pci-irq.c: Wrong message output

Mark F. Haigh wrote: --- arch/i386/kernel/pci-irq.c.orig 2005-02-07 19:55:23.852531544 -0800 +++ arch/i386/kernel/pci-irq.c 2005-02-07 20:13:38.835068896 -0800 Apologies. Patch now -p1-able. Mark F. Haigh [EMAIL PROTECTED] Signed-off-by: Mark F. Haigh [EMAIL PROTECTED] ---

Re: [PATCH 2.4.19-bk8] arch/i386/kernel/pci-irq.c: Wrong message output

Mark F. Haigh wrote: Apologies. Patch now -p1-able. [Apologies yet again, now includes description] I'd submitted a patch earlier for this file, fixing a warning. When I looked at it further, I noticed it can output an incorrect warning message under certain circumstances. I've confirmed that