From: "H. Peter Anvin" <hpa@zytor•com>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: Konrad Rzeszutek Wilk <konrad@kernel•org>,
Peter Jones <pjones@redhat•com>, Len Brown <lenb@kernel•org>,
linux-kernel@vger•kernel.org, gpxe-devel@etherboot•org,
linux-next@vger•kernel.org
Subject: Re: [PATCH] ibft: Use IBFT_SIGN instead of open-coding the search string.
Date: Wed, 12 May 2010 16:53:11 -0700 [thread overview]
Message-ID: <4BEB3F67.4050608@zytor.com> (raw)
In-Reply-To: <20100512123323.2badc5a7.akpm@linux-foundation.org>
On 05/12/2010 12:33 PM, Andrew Morton wrote:
> On Wed, 12 May 2010 10:35:32 -0400
> Konrad Rzeszutek Wilk <konrad@kernel•org> wrote:
>
>> Please also consider this patch with the others I've sent.
>> I've put this (and the other ones) on:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/ibft-2.6.git dev.ibft
>
> Well, you're the maintainer and you have a git tree and I cannot tell
> the difference between an IBFT and a bar of soap. So I suggest that
> you ask Stephen to permanently include your git tree in linux-next and
> send Linus a pull request in the 2.6.35-rc1 merge window like so many
> other people do?
>
Either that or send it via Len Brown, since iBFT really is an ACPI
extension.
-hpa
prev parent reply other threads:[~2010-05-13 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BEAB683.8040600@redhat.com>
[not found] ` <1273674308-9366-1-git-send-email-pjones@redhat.com>
[not found] ` <201005121035.33199.konrad@kernel.org>
2010-05-12 19:33 ` [PATCH] ibft: Use IBFT_SIGN instead of open-coding the search string Andrew Morton
2010-05-12 23:53 ` H. Peter Anvin [this message]
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=4BEB3F67.4050608@zytor.com \
--to=hpa@zytor$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=gpxe-devel@etherboot$(echo .)org \
--cc=konrad@kernel$(echo .)org \
--cc=lenb@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=pjones@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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