From: joeyli <jlee@suse.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: Matt Fleming <matt.fleming@intel.com>,
matthew.garrett@nebula.com, cbouatmailru@gmail.com,
ccross@android.com, keescook@chromium.org,
Tony Luck <tony.luck@intel.com>,
linux-efi@vger.kernel.org,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Cannot add new efi boot entry
Date: Wed, 17 Apr 2013 22:51:34 +0800 [thread overview]
Message-ID: <1366210294.23707.70.camel@linux-s257.site> (raw)
In-Reply-To: <1366210184.23707.69.camel@linux-s257.site>
於 三，2013-04-17 於 22:50 +0800，joeyli 提到：
> 於 三，2013-04-17 於 16:29 +0200，Jiri Slaby 提到：
> > On 04/16/2013 12:11 PM, Matt Fleming wrote:
> > > On 16/04/13 10:56, joeyli wrote:
> > >> I think I just got the same situation on my side with Acer machine. I am
> > >> trying Matthew's new patchset hope can avoid this situation:
> > >>
> > >> https://lkml.org/lkml/2013/4/15/473
> > >
> > > Please do let us know whether the patches work for you.
> >
> > Hmm, where did efi_query_variable_store in 3/3 come from?
> >
>
> here:
> https://git.kernel.org/cgit/linux/kernel/git/mfleming/efi.git/commit/?h=urgent&id=a6e4d5a03e9e3587e88aba687d8f225f4f04c792
>
> Matthew's 3 patches all merged to Matt's efi git tree.
Forgot mention, in urgent branch
>
>
> Thanks
> Joey Leeg
>
Joey Lee
next prev parent reply other threads:[~2013-04-17 14:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-14 21:25 Jiri Slaby
2013-04-16 9:56 ` joeyli
2013-04-16 10:11 ` Matt Fleming
2013-04-17 11:33 ` joeyli
2013-04-17 14:29 ` Jiri Slaby
2013-04-17 14:49 ` joeyli
2013-04-17 14:51 ` joeyli [this message]
2013-04-17 14:51 ` Matt Fleming
2013-04-18 18:07 ` Jiri Slaby
2013-04-20 7:40 ` Jiri Slaby
2013-04-22 11:07 ` Matt Fleming
2013-04-22 11:31 ` joeyli
2013-04-22 12:20 ` Matt Fleming
2013-04-22 12:25 ` Jiri Slaby
2013-04-22 16:43 ` Matthew Garrett
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=1366210294.23707.70.camel@linux-s257.site \
--to=jlee@suse.com \
--cc=cbouatmailru@gmail.com \
--cc=ccross@android.com \
--cc=jslaby@suse.cz \
--cc=keescook@chromium.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matthew.garrett@nebula.com \
--cc=tony.luck@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
Powered by JetHome