From: Matthew Garrett <matthew.garrett@nebula.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: Matt Fleming <matt@console-pimps.org>, joeyli <jlee@suse.com>,
"cbouatmailru@gmail.com" <cbouatmailru@gmail.com>,
"ccross@android.com" <ccross@android.com>,
"keescook@chromium.org" <keescook@chromium.org>,
Tony Luck <tony.luck@intel.com>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Cannot add new efi boot entry
Date: Mon, 22 Apr 2013 16:43:25 +0000 [thread overview]
Message-ID: <1366649004.13667.23.camel@x230.lan> (raw)
In-Reply-To: <51752C2C.4090707@suse.cz>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 688 bytes --]
On Mon, 2013-04-22 at 14:25 +0200, Jiri Slaby wrote:
> On 04/22/2013 02:20 PM, Matt Fleming wrote:
> > On 22/04/13 12:31, joeyli wrote:
> >> Does garbage collection only trigger by UEFI BIOS when system reboot? or
> >> garbage collection also triggered at run time?
> >
> > That is implementation specific. AFAIK, there are implementations for
> > both schemes.
>
> Just a point from the abstract level. Is there a way to find out? And
> what do Windows do?
Windows kills Samsungs.
--
Matthew Garrett | mjg59@srcf.ucam.org
ÿôèº{.nÇ+‰·Ÿ®‰†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a¢f£¢·hšïêÿ‘êçz_è®\x03(階ŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨èÚ&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥
prev parent reply other threads:[~2013-04-22 16:43 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
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 [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=1366649004.13667.23.camel@x230.lan \
--to=matthew.garrett@nebula.com \
--cc=cbouatmailru@gmail.com \
--cc=ccross@android.com \
--cc=jlee@suse.com \
--cc=jslaby@suse.cz \
--cc=keescook@chromium.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.org \
--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
all inboxes | Powered by JetHome®