From: Andrew Morton <akpm@linux-foundation.org>
To: Konrad Rzeszutek Wilk <konrad@kernel.org>
Cc: 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 12:33:23 -0700 [thread overview]
Message-ID: <20100512123323.2badc5a7.akpm@linux-foundation.org> (raw)
In-Reply-To: <201005121035.33199.konrad@kernel.org>
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?
next prev parent reply other threads:[~2010-05-12 19:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 14:21 [PATCH] Update iBFT to 1.03 Konrad Rzeszutek Wilk
2010-04-09 14:21 ` [PATCH 1/2] ibft: Update iBFT handling for v1.03 of the spec Konrad Rzeszutek Wilk
2010-04-21 21:26 ` Andrew Morton
2010-05-11 17:58 ` Konrad Rzeszutek Wilk
2010-05-12 5:26 ` Len Brown
2010-05-12 13:58 ` [LKML] " Konrad Rzeszutek Wilk
2010-05-12 14:09 ` Peter Jones
2010-05-12 14:12 ` [PATCH] Use IBFT_SIGN instead of open-coding the search string Peter Jones
2010-05-12 14:25 ` Peter Jones
2010-05-12 14:35 ` [PATCH] ibft: " Konrad Rzeszutek Wilk
2010-05-12 19:33 ` Andrew Morton [this message]
2010-05-12 23:53 ` H. Peter Anvin
2010-05-27 17:59 ` Konrad Rzeszutek Wilk
2010-04-09 14:21 ` [PATCH 2/2] ibft: For UEFI machines actually do scan ACPI for iBFT Konrad Rzeszutek Wilk
2010-04-21 21:29 ` Andrew Morton
2010-04-21 21:37 ` Mike Christie
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=20100512123323.2badc5a7.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gpxe-devel@etherboot.org \
--cc=konrad@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pjones@redhat.com \
/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).