From: Daniel J Blueman <daniel@numascale-asia.com>
To: Len Brown <lenb@kernel.org>
Cc: Joe Perches <joe@perches.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix printing when no interrupt is allocated
Date: Wed, 31 Oct 2012 17:03:00 +0800 [thread overview]
Message-ID: <5090E944.4020803@numascale-asia.com> (raw)
In-Reply-To: <1350609711.22385.21.camel@joe-AO722>
Hi Len,
On 19/10/2012 09:21, Joe Perches wrote:
> On Fri, 2012-10-19 at 08:33 +0800, Daniel J Blueman wrote:
>> Previously a new line is implicitly added in the no GSI case:
>>
>> [ 7.185182] pci 0001:00:12.0: can't derive routing for PCI INT A
>> [ 7.191352] pci 0001:00:12.0: PCI INT A: no GSI
>> [ 7.195956] - using ISA IRQ 10
>>
>> The code thus prints a blank line where no legacy IRQ is available:
>>
>> [ 1.650124] pci 0000:00:14.0: can't derive routing for PCI INT A
>> [ 1.650126] pci 0000:00:14.0: PCI INT A: no GSI
>> [ 1.650126]
>> [ 1.650180] pci 0000:00:14.0: can't derive routing for PCI INT A
>>
>> Fix this by making the newline explicit and removing the superfluous
>> one.
>
> I think this is a better fix:
>
> drivers/acpi/pci_irq.c | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/acpi/pci_irq.c b/drivers/acpi/pci_irq.c
> index 0eefa12..9b98f9f 100644
> --- a/drivers/acpi/pci_irq.c
> +++ b/drivers/acpi/pci_irq.c
> @@ -459,19 +459,20 @@ int acpi_pci_irq_enable(struct pci_dev *dev)
> */
> if (gsi < 0) {
> u32 dev_gsi;
> - dev_warn(&dev->dev, "PCI INT %c: no GSI", pin_name(pin));
> /* Interrupt Line values above 0xF are forbidden */
> if (dev->irq > 0 && (dev->irq <= 0xF) &&
> (acpi_isa_irq_to_gsi(dev->irq, &dev_gsi) == 0)) {
> - printk(" - using ISA IRQ %d\n", dev->irq);
> + dev_warn(&dev->dev,
> + "PCI INT %c: no GSI - using ISA IRQ %d\n",
> + pin_name(pin), dev->irq);
> acpi_register_gsi(&dev->dev, dev_gsi,
> ACPI_LEVEL_SENSITIVE,
> ACPI_ACTIVE_LOW);
> - return 0;
> } else {
> - printk("\n");
> - return 0;
> + dev_warn(&dev->dev, "PCI INT %c: no GSI\n",
> + pin_name(pin));
> }
> + return 0;
> }
>
> rc = acpi_register_gsi(&dev->dev, gsi, triggering, polarity);
We're still seeing this in 3.7-rc3. Any preference to the approach here?
Thanks,
Daniel
--
Daniel J Blueman
Principal Software Engineer, Numascale Asia
prev parent reply other threads:[~2012-10-31 9:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 0:33 Daniel J Blueman
2012-10-19 1:21 ` Joe Perches
2012-10-31 9:03 ` Daniel J Blueman [this message]
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=5090E944.4020803@numascale-asia.com \
--to=daniel@numascale-asia.com \
--cc=joe@perches.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.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®