From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>, Yinghai Lu <yinghai@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: state of some x86 acpi patches
Date: Sun, 15 Feb 2009 20:36:55 +0100 [thread overview]
Message-ID: <20090215193655.GA18674@elte.hu> (raw)
In-Reply-To: <20090209123711.GK17782@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
>
> * Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>
> > Yinghai Lu wrote:
> >> Ingo is too busy...
> >> It seems Len already agreed those patches can go through tip.
> >>
> >
> > OK, I have them prepared as a branch off tip/git pullable from:
> >
> > The following changes since commit 82eda818f26cbef2b0a6bf6580e52645af62e4fd:
> > Ingo Molnar (1):
> > Merge branch 'core/locking'
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git acpi/map
> >
> > Jeremy Fitzhardinge (3):
> > x86: use early_ioremap in __acpi_map_table
> > x86: always explicitly map acpi memory
> > acpi: remove final __acpi_map_table mapping before setting acpi_gbl_permanent_mmap
> >
> > Yinghai Lu (2):
> > acpi/x86: introduce __apci_map_table, v4
> > revert_fix_es7000_compiling
> >
> > arch/ia64/kernel/acpi.c | 4 ++++
> > arch/x86/include/asm/acpi.h | 3 ---
> > arch/x86/include/asm/fixmap_32.h | 4 ----
> > arch/x86/include/asm/fixmap_64.h | 4 ----
> > arch/x86/kernel/acpi/boot.c | 33 ++++++++-------------------------
> > arch/x86/kernel/es7000_32.c | 9 ++++++++-
> > drivers/acpi/acpica/tbxface.c | 17 ++++++++++++++---
> > drivers/acpi/osl.c | 11 +++++++++--
> > drivers/acpi/tables.c | 20 ++++++++++++++------
> > include/acpi/acpiosxf.h | 1 +
> > include/acpi/acpixf.h | 4 ++++
> > include/linux/acpi.h | 1 +
> > 12 files changed, 63 insertions(+), 48 deletions(-)
>
> Ok, pulled into tip:x86/acpi, thanks guys!
Note, there's a new ia64 build failure due to these patches:
/home/mingo/tip/arch/ia64/kernel/acpi.c:203: error: conflicting types for '__acpi_unmap_table'
/home/mingo/tip/include/linux/acpi.h:82: error: previous declaration of '__acpi_unmap_table' was here
/home/mingo/tip/arch/ia64/kernel/acpi.c:203: error: conflicting types for '__acpi_unmap_table'
/home/mingo/tip/include/linux/acpi.h:82: error: previous declaration of '__acpi_unmap_table' was here
make[2]: *** [arch/ia64/kernel/acpi.o] Error 1
make[2]: *** Waiting for unfinished jobs....
/home/mingo/tip/arch/ia64/kernel/ivt.S: Assembler messages:
Ingo
next prev parent reply other threads:[~2009-02-15 19:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4947FF4C.80706@goop.org>
[not found] ` <20081216192534.GB843@elte.hu>
[not found] ` <alpine.LFD.2.00.0812311821110.3854@localhost.localdomain>
[not found] ` <495C677F.6080707@goop.org>
[not found] ` <20090102153957.GA1180@elte.hu>
[not found] ` <4980EE0C.4070308@goop.org>
[not found] ` <49810211.9030808@kernel.org>
[not found] ` <498CF8DA.30004@goop.org>
2009-02-07 3:18 ` state of some x86 acpi patches Yinghai Lu
2009-02-08 0:09 ` Jeremy Fitzhardinge
2009-02-09 12:37 ` Ingo Molnar
2009-02-15 19:36 ` Ingo Molnar [this message]
2009-02-15 22:06 ` Yinghai Lu
2009-02-15 22:25 ` Ingo Molnar
2009-02-15 22:46 ` Ingo Molnar
2009-02-15 23:10 ` Yinghai Lu
2009-02-20 21:54 ` Tony Luck
2009-02-20 21:55 ` Yinghai Lu
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=20090215193655.GA18674@elte.hu \
--to=mingo@elte.hu \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yinghai@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