From: Rene Herman <rene.herman@keyaccess.nl>
To: David Howells <dhowells@redhat.com>
Cc: bjorn.helgaas@hp.com, rene.herman@gmail.com, len.brown@intel.com,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH] Fix pnpacpi_parse_irq_option()'s test against PNP_IRQ_NR
Date: Fri, 27 Jun 2008 17:26:28 +0200 [thread overview]
Message-ID: <486506A4.7060605@keyaccess.nl> (raw)
In-Reply-To: <16399.1214578444@redhat.com>
On 27-06-08 16:54, David Howells wrote:
> Rene Herman <rene.herman@keyaccess.nl> wrote:
>
>> Well, it's been promoted from a u8, so no need for that anyway, but <shrug>.
>
> My logic is that in commit 95b24192cf27631dc11541e97c430389320e7a93 it says
> the following:
>
> ACPI Extended Interrupt Descriptors can encode 32-bit interrupt
> numbers, so an interrupt number may exceed the size of the bitmap
> we use to track possible IRQ settings.
>
> so the field in 'struct acpi_resource_irq' might at some point increase to be
> a 32-bit unsigned value. Otherwise there's no point having the check at all,
> right?
Ah, how lovely, there has been a merge error at some point...
No, that larger value would live in a struct acpi_resource_extended_irq.
This code was supposed to go in pnpacpi_parse_ext_irq_option() instead.
Here's the original posting of this patch:
http://lkml.org/lkml/2008/5/30/390
where it indeed is. Here is the last one, where it has mistakingly
shifted position to pnpacpi_parse_irq_option():
http://lkml.org/lkml/2008/6/17/337
I was already wondering why I hadn't see that warning myself while I was
testing things...
Bjorn?
Rene.
next prev parent reply other threads:[~2008-06-27 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 12:33 [PATCH] Fix pnpacpi_parse_irq_option()'s test against PNP_IRQ_NR David Howells
2008-06-27 12:53 ` Rene Herman
2008-06-27 13:16 ` David Howells
2008-06-27 13:38 ` Rene Herman
2008-06-27 14:54 ` David Howells
2008-06-27 15:14 ` Bjorn Helgaas
2008-06-27 15:26 ` Rene Herman [this message]
2008-06-27 15:38 ` Rene Herman
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=486506A4.7060605@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=bjorn.helgaas@hp.com \
--cc=dhowells@redhat.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rene.herman@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).