public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Mark F. Haigh" <Mark.Haigh@spirentcom.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.11-rc3-bk4] arch/i386/kernel/pci/irq.c:  Wrong message output
Date: Mon, 7 Feb 2005 21:34:41 -0800	[thread overview]
Message-ID: <20050208053441.GA31216@suse.de> (raw)
In-Reply-To: <420848CA.2030008@spirentcom.com>

On Mon, Feb 07, 2005 at 09:06:18PM -0800, Mark F. Haigh wrote:
> 
> (Same basic problem I just reported in a seperate thread against 2.4.29-bk8)
> 
> The following has been reported in the wild for kernel 2.6.8-24:
> 
> PCI: Enabling device 0000:00:05.0 (0000 -> 0002)
> PCI: No IRQ known for interrupt pin @ of device 0000:00:05.0. Probably 
> buggy MP table.
> 
> It should read "No IRQ known for interrupt pin A", but the 'pin' 
> variable has already been decremented (from 1 to 0), so the line:
> 
> printk(KERN_WARNING "PCI: No IRQ known for interrupt pin %c of device 
> %s.%s\n", 'A' + pin - 1, dev->slot_name, msg);
> 
> causes "pin @" to be output, because 'A' + 0 - 1 == '@'.
> 
> The supplied patch should fix it.  It also removes a redundant check for 
> a nonzero pin.
> 
> 
> Mark F. Haigh
> Mark.Haigh@spirentcom.com
> 

> --- arch/i386/pci/irq.c.orig	2005-02-07 20:40:58.140856536 -0800
> +++ arch/i386/pci/irq.c	2005-02-07 20:46:06.713946296 -0800

Can you resend this so it can be applied with -p1 to patch, and a
Signed-off-by: line?

thanks,

greg k-h

  reply	other threads:[~2005-02-08  5:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08  5:06 [PATCH 2.6.11-rc3-bk4] arch/i386/kernel/pci/irq.c: Wrong message output Mark F. Haigh
2005-02-08  5:34 ` Greg KH [this message]
2005-02-08  5:42   ` Mark F. Haigh
2005-02-08  5:52     ` Greg KH
2005-02-08  6:07       ` Mark F. Haigh

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=20050208053441.GA31216@suse.de \
    --to=greg@kroah.com \
    --cc=Mark.Haigh@spirentcom.com \
    --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