public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Matt Porter <matt.porter@linaro.org>
Cc: Davidlohr Bueso <davidlohr@hp.com>,
	Matt Fleming <matt.fleming@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	torvalds@linux-foundation.org
Subject: Re: GPT detection regression in efi.c from commit 27a7c64
Date: Fri, 13 Sep 2013 20:17:20 +0200	[thread overview]
Message-ID: <20130913181720.GA1614@x2.net.home> (raw)
In-Reply-To: <523354F3.70001@linaro.org>

On Fri, Sep 13, 2013 at 02:09:55PM -0400, Matt Porter wrote:
> >Come to think of it, we do have a long existing workaround: the
> >force_gpt option. Setting it will bypass any MBR checking
> >(is_pmbr_valid(), specifically).
> 
> Yes, that's what I used at first after seeing what the problem was. But then
> I opted to fix my PMBR.
> 
> I felt like it was a regression since it required a new option passed on the
> cmdline.

 Yep, it is *regression* and I guess Davidlohr is going to fix it asap :-)

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  reply	other threads:[~2013-09-13 18:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-13 14:50 GPT detection regression in efi.c from commit 27a7c64 Matt Porter
2013-09-13 16:28 ` Davidlohr Bueso
2013-09-13 17:01   ` Matt Porter
2013-09-13 17:37     ` Davidlohr Bueso
2013-09-13 18:17       ` Matt Porter
2013-09-13 18:07     ` Davidlohr Bueso
2013-09-13 18:09       ` Matt Porter
2013-09-13 18:17         ` Karel Zak [this message]
2013-09-13 18:29           ` Davidlohr Bueso
2013-09-13 18:33             ` Matt Porter
2013-09-13 19:26               ` Davidlohr Bueso
2013-09-13 21:36                 ` Matt Porter
2013-09-13 22:02                   ` Davidlohr Bueso

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=20130913181720.GA1614@x2.net.home \
    --to=kzak@redhat.com \
    --cc=davidlohr@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=matt.porter@linaro.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox