From: Jochen Hein <jochen@jochen.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: andrew.grover@intel.com, trivial@rustcorp.com.au,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [TRIVIAL, RESEND][ACPI, PCI] boot messages need line feeds
Date: Fri, 07 Feb 2003 17:44:54 +0100 [thread overview]
Message-ID: <87of5o9h15.fsf@gswi1164.jochen.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2343 bytes --]
[This time sent to Linus, CC to Andrew Grover and the Trivial Patch
Monkey]
The messages are:
pci_link-0331 [15] acpi_pci_link_set : Link disabled
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 0
pci_link-0331 [15] acpi_pci_link_set : Link disabled
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 0
pci_link-0331 [15] acpi_pci_link_set : Link disabled
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 0
pci_link-0331 [15] acpi_pci_link_set : Link disabled
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 0
pci_link-0484 [16] acpi_pci_link_get_irq : Link disabled
pci_irq-0256 [15] acpi_pci_irq_lookup : Invalid IRQ link routing entry
pci_irq-0295 [15] acpi_pci_irq_derive : Unable to derive IRQ for device 00:02.0
ACPI: No IRQ known for interrupt pin A of device 00:02.0 - using IRQ 255
pci_link-0484 [16] acpi_pci_link_get_irq : Link disabled
pci_irq-0256 [15] acpi_pci_irq_lookup : Invalid IRQ link routing entry
pci_irq-0295 [15] acpi_pci_irq_derive : Unable to derive IRQ for device 00:02.1
ACPI: No IRQ known for interrupt pin B of device 00:02.1 - using IRQ 255
pci_link-0484 [16] acpi_pci_link_get_irq : Link disabled
pci_irq-0256 [15] acpi_pci_irq_lookup : Invalid IRQ link routing entry
pci_irq-0295 [15] acpi_pci_irq_derive : Unable to derive IRQ for device 00:03.0
ACPI: No IRQ known for interrupt pin A of device 00:03.0pci_link-0484 [16] acpi_pci_link_get_irq : Link disabled
^I think, here
should be a line feed. Next messages:
pci_irq-0256 [15] acpi_pci_irq_lookup : Invalid IRQ link routing entry
pci_irq-0295 [15] acpi_pci_irq_derive : Unable to derive IRQ for device 00:07.2
ACPI: No IRQ known for interrupt pin D of device 00:07.2<6>PCI: Using ACPI for IRQ routing
^and again.
The following patch fixes it.
--- linux-2.5.59/drivers/acpi/pci_irq.c.jh 2003-01-25 10:09:10.000000000 +0100
+++ linux-2.5.59/drivers/acpi/pci_irq.c 2003-01-25 10:10:54.000000000 +0100
@@ -351,8 +351,10 @@
printk(" - using IRQ %d\n", dev->irq);
return_VALUE(dev->irq);
}
- else
+ else {
+ printk("\n");
return_VALUE(0);
+ }
}
dev->irq = irq;
Jochen
--
Wenn Du nicht weißt was Du tust, tu's mit Eleganz.
[-- Attachment #2: Type: text/plain, Size: 59 bytes --]
--
Wenn Du nicht weißt was Du tust, tu's mit Eleganz.
next reply other threads:[~2003-02-07 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 16:44 Jochen Hein [this message]
2003-02-07 18:04 Grover, Andrew
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87of5o9h15.fsf@gswi1164.jochen.org \
--to=jochen@jochen.org \
--cc=andrew.grover@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=trivial@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®