From: Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>
To: Matt Fleming <matt.fleming@intel.com>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware: efi: remove unneeded guid unparse
Date: Thu, 29 Jan 2015 16:57:29 +0200 [thread overview]
Message-ID: <54CA4A59.7000905@linaro.org> (raw)
In-Reply-To: <1422542869.21110.8.camel@mfleming-mobl1.ger.corp.intel.com>
Oh, sorry.
Just didn't note that it's picked up from linaro list.
On 01/29/2015 04:47 PM, Matt Fleming wrote:
> On Thu, 2015-01-29 at 16:35 +0200, Ivan Khoronzhuk wrote:
>> There is no reason to translate guid number to string here.
>> So remove it in order to not do unneeded work.
>>
>> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>
>> ---
>> drivers/firmware/efi/efi.c | 5 -----
>> 1 file changed, 5 deletions(-)
> Why the resend? I already picked this commit up,
>
> https://lkml.kernel.org/r/20150120223238.GC12079@codeblueprint.co.uk
>
prev parent reply other threads:[~2015-01-29 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 14:35 [PATCH] firmware: efi: remove unneeded guid unparse Ivan Khoronzhuk
2015-01-29 14:47 ` Matt Fleming
2015-01-29 14:57 ` Ivan Khoronzhuk [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=54CA4A59.7000905@linaro.org \
--to=ivan.khoronzhuk@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.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