From: Ingo Molnar <mingo@elte.hu>
To: Len Brown <lenb@kernel.org>
Cc: x86@kernel.org, sfi-devel@simplefirmware.org,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH 00/11] SFI: Simple Firmware Interface - v3
Date: Mon, 17 Aug 2009 12:06:28 +0200 [thread overview]
Message-ID: <20090817100628.GA21498@elte.hu> (raw)
In-Reply-To: <1250282295-25216-1-git-send-email-lenb@kernel.org>
* Len Brown <lenb@kernel.org> wrote:
> Changes since v2:
>
> re-based to v2.6.31-rc6
>
> included here some patches from the ACPI tree
> that prepare for SFI
>
> deleted MMAP table parsing code
> It isn't needed in the kernel, since on all known SFI boxes today,
> the booter parses this table for us.
>
> fixed some build issues, generally related to CONFIG_ACPI=n
>
> various cosmetic changes in response to v2 code review
>
> What is left to do:
>
> x86_32 can set CONFIG_PCI_MMCONFIG=y when
> SFI=y and ACPI=n, but x86_64 can not, yet.
>
> A number of drivers will use SFI and will provide
> their own table parsers, but those will come later.
Ok, this iteration is even nicer.
Reviewed-by: Ingo Molnar <mingo@elte.hu>
A patch technical request/suggestion. I guess you'd like to keep
these bits in the ACPI tree, so that you can test it and merge it
with ongoing ACPI changes, right?
That would be fine to me for all the arch/x86/ touching patches,
except for this one:
[PATCH 05/11] ACPI, x86: expose some IO-APIC routines when CONFIG_ACPI=n
I'd like to pick this one up into tip:x86/apic, because there's
ongoing work in this area. (also, by the looks of it, i'd not be
surprised if this patch needed some testing. This is fragile code
with quirky Kconfig dependencies.)
I can create a standalone topic for this (based on .31-rc6),
containing this single commit, which you could pull into the ACPI
tree? That way we both can have this commit and nobody is held up,
and both trees can be pushed to Linus in the .32 merge window,
independently of each other.
Ingo
next prev parent reply other threads:[~2009-08-17 10:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 20:38 [PATCH 00/11] SFI: Simple Firmware Interface - v3 Len Brown
2009-08-14 20:38 ` [PATCH 01/11] ACPI: Move definition of PREFIX from acpi_bus.h to internal..h Len Brown
2009-08-14 20:38 ` [PATCH 02/11] ACPI, PCI: Change PREFIX to "PCI" from "ACPI" in mmconfig-shared.c Len Brown
2009-08-14 20:38 ` [PATCH 03/11] ACPI: check acpi_disabled in acpi_table_parse() and acpi_table_parse_entries() Len Brown
2009-08-14 20:38 ` [PATCH 04/11] ACPI: Handle CONFIG_ACPI=n better from linux/acpi.h Len Brown
2009-08-14 20:38 ` [PATCH 05/11] ACPI, x86: expose some IO-APIC routines when CONFIG_ACPI=n Len Brown
2009-08-14 20:38 ` [PATCH 06/11] SFI: Simple Firmware Interface - MAINTAINERS, Kconfig Len Brown
2009-08-14 20:38 ` [PATCH 07/11] SFI: create linux/sfi.h Len Brown
2009-08-14 20:38 ` [PATCH 08/11] SFI: add platform-independent core support Len Brown
2009-08-14 20:38 ` [PATCH 09/11] SFI: add capability to parse ACPI tables Len Brown
2009-08-14 20:38 ` [PATCH 10/11] x86: add arch-specific SFI support Len Brown
2009-08-14 20:38 ` [PATCH 11/11] SFI: Hook PCI MMCONFIG Len Brown
2009-08-17 10:06 ` Ingo Molnar [this message]
2009-08-29 0:14 ` [PATCH 00/11] SFI: Simple Firmware Interface - v3 Len Brown
2009-08-29 7:34 ` Ingo Molnar
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=20090817100628.GA21498@elte.hu \
--to=mingo@elte.hu \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfi-devel@simplefirmware.org \
--cc=x86@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