mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jochen Hein <jochen@jochen.org>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [TRIVIAL][ACPI, PCI] boot messages need line feeds
Date: Sat, 25 Jan 2003 10:13:27 +0100	[thread overview]
Message-ID: <87iswdsibs.fsf@gswi1164.jochen.org> (raw)


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 sould fix it, but is for now untested:

--- 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.

                 reply	other threads:[~2003-01-25 17:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87iswdsibs.fsf@gswi1164.jochen.org \
    --to=jochen@jochen.org \
    --cc=linux-kernel@vger.kernel.org \
    /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®