| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 23 Jun 2009 16:02:25 +0800 From: Feng Tang <feng.tang@...el.com> To: Ingo Molnar <mingo@...e.hu> CC: Len Brown <lenb@...nel.org>, "sfi-devel@...plefirmware.org" <sfi-devel@...plefirmware.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "Brown, Len" <len.brown@...el.com>, "Thomas Gleixner" <tglx@...utronix.de>, "H. Peter Anvin" <hpa@...or.com>, Yinghai Lu <yinghai@...nel.org> Subject: Re: [PATCH 2/8] SFI: include/linux/sfi.h On Tue, 23 Jun 2009 16:00:47 +0800 Ingo Molnar <mingo@...e.hu> wrote: > > * Feng Tang <feng.tang@...el.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? AFAIK, Len's target is for 2.6.32 Thanks, Feng > > Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists