All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Fleming, Matt" <matt.fleming@intel.com>
To: joeyli <jlee@suse.com>
Cc: Matthew Garrett <matthew.garrett@nebula.com>,
	"rja@sgi.com" <rja@sgi.com>,
	"mingo@kernel.org" <mingo@kernel.org>,
	"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
	"bp@alien8.de" <bp@alien8.de>,
	"jkosina@suse.cz" <jkosina@suse.cz>,
	"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"hpa@linux.intel.com" <hpa@linux.intel.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"oneukum@suse.de" <oneukum@suse.de>
Subject: Re: [PATCH] Modify UEFI anti-bricking code
Date: Wed, 5 Jun 2013 15:49:45 +0100	[thread overview]
Message-ID: <CAL01qptzxe5L6Vq+nBZLq+bQNxbe_i_2OdKMNJGZQDfMihaHOw@mail.gmail.com> (raw)
In-Reply-To: <1370316933.30695.7.camel@linux-s257.site>

On 4 June 2013 04:35, joeyli <jlee@suse.com> wrote:
> 於 一，2013-06-03 於 16:31 +0000，Matthew Garrett 提到：
>> On Tue, 2013-06-04 at 00:13 +0800, joeyli wrote:
>>
>> > Oliver raised a question for if power fails between that succesful
>> > attempt and the deletion?
>>
>> It's a pretty tiny window, but sure. Making sure we delete it seems
>> sensible. In that case we should make the GUID a #define rather than
>> write it out twice.
>>
>
> Base on your patch, the following diff moved DUMMY GUID to #define, and
> add a static efi name string:

Folks, what do you want me to do with this? Merge it with Matthew's patch?

The feedback from the original patch has been pretty good so I'm happy
to pick it up and get it sent to Linus.

  reply	other threads:[~2013-06-05 14:49 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-01 20:06 [PATCH] Modify UEFI anti-bricking code Matthew Garrett
2013-06-01 20:06 ` Matthew Garrett
2013-06-02 15:48 ` Russ Anderson
2013-06-02 15:48   ` Russ Anderson
2013-06-03 12:17 ` Matt Fleming
2013-06-03 14:58   ` Matthew Garrett
2013-06-03 14:58     ` Matthew Garrett
2013-06-03 16:13 ` joeyli
2013-06-03 16:31   ` Matthew Garrett
2013-06-03 16:31     ` Matthew Garrett
2013-06-04  3:35     ` joeyli
2013-06-04  3:35       ` joeyli
2013-06-05 14:49       ` Fleming, Matt [this message]
2013-06-05 14:53         ` Matthew Garrett
2013-06-05 14:53           ` Matthew Garrett
2013-06-05 15:59           ` Matt Fleming
2013-06-05 15:59             ` Matt Fleming
2013-06-05 16:08             ` Matthew Garrett
2013-06-05 16:08               ` Matthew Garrett
2013-06-05 19:59               ` Matt Fleming
2013-06-05 19:59                 ` Matt Fleming
2013-06-06  2:24               ` joeyli
2013-06-05 20:19             ` H. Peter Anvin
2013-06-05 20:19               ` H. Peter Anvin
2013-06-06  5:05             ` joeyli
2013-06-06  5:05               ` joeyli
2013-06-06  5:41               ` joeyli
2013-06-06  5:42               ` Matthew Garrett
2013-06-06  5:42                 ` Matthew Garrett
2013-06-06  7:40                 ` joeyli
2013-06-06  7:40                   ` joeyli
2013-06-06  9:25                   ` Matt Fleming
2013-06-06  9:25                     ` Matt Fleming
2013-06-06 14:48                     ` Russ Anderson
2013-06-06 14:48                       ` Russ Anderson
2013-06-06 15:00                       ` Matt Fleming
2013-06-06 15:00                         ` Matt Fleming
2013-06-06 15:28                         ` Russ Anderson
2013-06-06 15:28                           ` Russ Anderson
2013-06-10 18:54                     ` Russ Anderson
2013-06-10 18:54                       ` Russ Anderson
2013-06-04  5:29 ` Lingzhu Xiang
2013-06-04  5:29   ` Lingzhu Xiang

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=CAL01qptzxe5L6Vq+nBZLq+bQNxbe_i_2OdKMNJGZQDfMihaHOw@mail.gmail.com \
    --to=matt.fleming@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=hpa@linux.intel.com \
    --cc=jkosina@suse.cz \
    --cc=jlee@suse.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.garrett@nebula.com \
    --cc=mingo@kernel.org \
    --cc=oneukum@suse.de \
    --cc=rja@sgi.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.