All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Feng Tang <feng.tang@intel.com>
Cc: Len Brown <lenb@kernel.org>,
	"sfi-devel@simplefirmware.org" <sfi-devel@simplefirmware.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Brown, Len" <len.brown@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>, Yinghai Lu <yinghai@kernel.org>
Subject: Re: [PATCH 2/8] SFI: include/linux/sfi.h
Date: Tue, 23 Jun 2009 10:00:47 +0200	[thread overview]
Message-ID: <20090623080047.GE6397@elte.hu> (raw)
In-Reply-To: <20090623154724.08a51ea3@feng-desktop>


* Feng Tang <feng.tang@intel.com> wrote:

> For these arch_early_ioremap/arch_early_iounmap API, do you mean 
> we should put it in a sfi.h under "asm" folder? The reason we put 
> it here is to give a arch independent API declaration here and let 
> each arch implement its own func.

Yeah, i'd suggest to create a new early-remap.h and early-remap.c 
kind of file to collect the existing bits for that. It's a bit ugly 
(not really the fault of SFI - these are pre-existing facilities) 
and might need some love - we better move it apart so that the light 
of attention shines on it.

What's the target merge of the SFI stuff, 2.6.31?

	Ingo

  reply	other threads:[~2009-06-23  8:01 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23  7:13 [RFC/PATCH 2.6.32] Simple Firmware Interface (SFI): initial support Len Brown
2009-06-23  7:13 ` [PATCH 1/8] SFI: Simple Firmware Interface - new Linux sub-system Len Brown
2009-06-23  7:14   ` [PATCH 2/8] SFI: include/linux/sfi.h Len Brown
2009-06-23  7:28     ` Ingo Molnar
2009-06-23  7:47       ` Feng Tang
2009-06-23  8:00         ` Ingo Molnar [this message]
2009-06-23  8:02           ` Feng Tang
2009-06-23  8:09             ` Ingo Molnar
2009-06-23 15:14               ` H. Peter Anvin
2009-06-30 21:57       ` Andrew Morton
2009-06-30 21:59         ` Ingo Molnar
2009-06-23  9:06     ` Sam Ravnborg
2009-06-23 15:52       ` Feng Tang
2009-06-23 19:26         ` Sam Ravnborg
2009-06-23  7:14   ` [PATCH 3/8] SFI: core support Len Brown
2009-06-23  7:56     ` Ingo Molnar
2009-06-23  8:32       ` Feng Tang
2009-06-23  9:03         ` Ingo Molnar
2009-06-23  9:15           ` Feng Tang
2009-06-23 17:20       ` Len Brown
2009-06-23 19:20         ` Ingo Molnar
2009-06-23 12:32     ` Andi Kleen
2009-06-23 16:57       ` Len Brown
2009-06-24  3:34       ` Feng Tang
2009-06-24  7:12         ` Andi Kleen
2009-06-24  7:40           ` Feng Tang
2009-06-24  7:55             ` Andi Kleen
2009-06-23  7:14   ` [PATCH 4/8] SFI: Hook boot-time initialization Len Brown
2009-06-23  7:14   ` [PATCH 5/8] SFI: Hook e820 memory map initialization Len Brown
2009-06-23  7:14   ` [PATCH 6/8] SFI: add ACPI extensions Len Brown
2009-06-23 12:18     ` Andi Kleen
2009-06-23 16:51       ` Len Brown
2009-06-23  7:14   ` [PATCH 7/8] SFI, PCI: Hook MMCONFIG Len Brown
2009-06-23  7:14   ` [PATCH 8/8] SFI: expose IO-APIC routines to SFI, not just ACPI Len Brown
2009-06-23  7:58     ` Ingo Molnar
2009-06-23  7:23   ` [PATCH 1/8] SFI: Simple Firmware Interface - new Linux sub-system Ingo Molnar
2009-06-23 18:31 ` [RFC/PATCH 2.6.32] Simple Firmware Interface (SFI): initial support Matthew Garrett
2009-06-23 18:41   ` Len Brown
2009-06-22 19:43     ` Pavel Machek
2009-06-24 21:13       ` Len Brown
2009-07-11 22:02         ` Pavel Machek
2009-07-13  3:25           ` [SFI-devel] " Peter Stuge
2009-06-23 18:51     ` Matthew Garrett
2009-06-23 20:00       ` Len Brown
2009-06-23 20:23         ` Matthew Garrett
2009-06-23 20:45           ` Matthew Garrett
2009-06-23 21:23             ` Alan Cox
2009-06-23 22:34               ` Len Brown
2009-06-23 22:20             ` Len Brown
2009-06-23 22:56               ` Matthew Garrett
2009-06-23 23:00               ` [SFI-devel] " Justen, Jordan L
2009-06-24  0:35                 ` Len Brown
2009-06-23 21:33           ` Len Brown

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=20090623080047.GE6397@elte.hu \
    --to=mingo@elte.hu \
    --cc=feng.tang@intel.com \
    --cc=hpa@zytor.com \
    --cc=len.brown@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfi-devel@simplefirmware.org \
    --cc=tglx@linutronix.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.