From: Florian Mickler <florian@mickler.org>
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
Len Brown <lenb@kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
kurup_avinash@yahoo.com, maciej.rutecki@gmail.com, rjw@sisk.pl,
sedat.dilek@gmail.com
Subject: Re: [PATCH] x86, ioapic: move acpi_get_override_irq to acpi.c
Date: Fri, 1 Apr 2011 18:26:53 +0200 [thread overview]
Message-ID: <20110401182653.340abaa4@schatten.dmk.lab> (raw)
In-Reply-To: <1301672686-10096-1-git-send-email-florian@mickler.org>
On Fri, 1 Apr 2011 17:44:46 +0200
Florian Mickler <florian@mickler.org> wrote:
>
> Hi Ingo,
>
> Instead of exporting find_irq_entry, irq_trigger and irq_polarity, I added a
> new helper function 'ioapic_get_irq(..)' and exported that.
>
> Also I did it as a seperate commit, since it is more of a cleanup and the other
> commit is already tested... hope this is ok.
>
> Regards,
> Flo
>
btw, include/linux/acpi.h:
120
121 #ifdef CONFIG_X86_IO_APIC
122 extern int acpi_get_override_irq(u32 gsi, int *trigger, int *polarity);
123 #else
124 #define acpi_get_override_irq(gsi, trigger, polarity) (-1)
125 #endif
this shouldn't be needed anymore, as acpi_get_override_irq is now
independent of CONFIG_X86_IO_APIC (because of ioapic_get_irq having
a placeholder in the !CONFIG_X86_IO_APIC case)
But on the other hand, the code flow for the !CONFIG_X86_IO_APIC would
be kind of silly... what's the rationale for mp_find_ioapic returning
0 in the !CONFIG_X86_IO_APIC case? And how do I check compilation
of !CONFIG_X86_IO_APIC? It looks like it already has problems, as
mp_find_ioapic_pin is not stubbed out, or am I overlooking something?
Regards,
Flo
next prev parent reply other threads:[~2011-04-01 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110401075011.GD7594@elte.hu>
2011-04-01 15:44 ` [PATCH] x86, ioapic: move acpi_get_override_irq to acpi.c Florian Mickler
2011-04-01 16:26 ` Florian Mickler [this message]
2011-04-03 14:34 ` Florian Mickler
2011-04-04 15:00 ` Ingo Molnar
2011-04-12 7:39 ` Ingo Molnar
2011-04-12 19:53 ` Florian Mickler
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=20110401182653.340abaa4@schatten.dmk.lab \
--to=florian@mickler.org \
--cc=ebiederm@xmission.com \
--cc=kurup_avinash@yahoo.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=sedat.dilek@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