linux-kernel - Re: Re-add ibft tree to linux-next please

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 12 Dec 2011 15:25:11 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Konrad Rzeszutek Wilk <konrad@...nel.org>,
	"Brown, Len" <len.brown@...el.com>, linux-acpi@...r.kernel.org
CC:	sfr@...b.auug.org.au, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org, pjones@...hat.com
Subject: Re: Re-add ibft tree to linux-next please

On 12/12/2011 06:53 AM, Konrad Rzeszutek Wilk wrote:
> Hey Stephen,
> 
> I've one patch for the iBFT and since I am the co-maintainer of said tree,
> please add this tree to your awesome build system:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/ibft.git
> 
> The branch is "linux-next"
> 
> Signed-off-by: Konrad Rzeszutek Wilk <konrad@...nel.org>
> CC: Peter Jones <pjones@...hat.com>
> Thanks!
> 
> P.S.
> After kernel.org went down, I choose not to resurface the iBFT tree b/c I
> figured that the driver was sooo stable that there would be no need for any
> patches. Well, not the case

iBFT is basically an ACPI table with nonstandard discovery.  Any way we
could get this merged into the ACPI core eventually?

	-hpa

--
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/