From: Matt Fleming <matt@console-pimps.org>
To: Madper Xie <cxie@redhat.com>
Cc: Matt Fleming <matt.fleming@intel.com>,
Richard Weinberger <richard@nod.at>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>
Subject: Re: [PATCH] EFI: Delete out-of-date comments of efi_query_variable_store
Date: Mon, 11 Nov 2013 16:14:57 +0000 [thread overview]
Message-ID: <20131111161457.GI22636@console-pimps.org> (raw)
In-Reply-To: <87y54wny1c.fsf@redhat.com>
On Sun, 10 Nov, at 10:15:11PM, Madper Xie wrote:
>
> For now we only ensure about 5kb free space for avoiding our board
> refusing boot. But the comment lies that we retain 50% space.
>
> Signed-off-by: Madper Xie <cxie@redhat.com>
> ---
> arch/x86/platform/efi/efi.c | 12 +++++-------
> 1 file changed, 5 insertions(+), 7 deletions(-)
Applied, thanks.
--
Matt Fleming, Intel Open Source Technology Center
prev parent reply other threads:[~2013-11-11 16:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-10 14:15 [PATCH] EFI: Delete out-of-date comments of efi_query_variable_store Madper Xie
2013-11-11 16:14 ` Matt Fleming [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=20131111161457.GI22636@console-pimps.org \
--to=matt@console-pimps.org \
--cc=cxie@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=richard@nod.at \
/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