linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Konrad Rzeszutek Wilk <konrad@kernel.org>,
	"Brown, Len" <len.brown@intel.com>,
	linux-acpi@vger.kernel.org
Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org,
	linux-kernel@vger.kernel.org, pjones@redhat.com
Subject: Re: Re-add ibft tree to linux-next please
Date: Mon, 12 Dec 2011 15:25:11 -0800	[thread overview]
Message-ID: <4EE68D57.7030603@zytor.com> (raw)
In-Reply-To: <20111212145330.GA16278@andromeda.dapyr.net>

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@kernel.org>
> CC: Peter Jones <pjones@redhat.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


       reply	other threads:[~2011-12-12 23:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20111212145330.GA16278@andromeda.dapyr.net>
2011-12-12 23:25 ` H. Peter Anvin [this message]
2011-12-13  2:15   ` Re-add ibft tree to linux-next please Konrad Rzeszutek Wilk
2012-01-17 14:08     ` Len Brown
2012-01-17 16:49       ` Konrad Rzeszutek Wilk
2012-01-17 17:37         ` H. Peter Anvin

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=4EE68D57.7030603@zytor.com \
    --to=hpa@zytor.com \
    --cc=konrad@kernel.org \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=pjones@redhat.com \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).