From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: Re-add ibft tree to linux-next please Date: Mon, 12 Dec 2011 15:25:11 -0800 Message-ID: <4EE68D57.7030603@zytor.com> References: <20111212145330.GA16278@andromeda.dapyr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20111212145330.GA16278@andromeda.dapyr.net> Sender: linux-acpi-owner@vger.kernel.org To: Konrad Rzeszutek Wilk , "Brown, Len" , linux-acpi@vger.kernel.org Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, pjones@redhat.com List-Id: linux-next.vger.kernel.org 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 > CC: Peter Jones > 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