From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH V3 1/3] Update the Linux boot protocol
Date: Sun, 26 Feb 2012 22:29:07 +0100 [thread overview]
Message-ID: <4F4AA423.9020102@gmail.com> (raw)
In-Reply-To: <CAMPnHXw6B+-mfMu0szBuk=Ukp_bJDx4hrpLLNkEmgwFkiLdK3w@mail.gmail.com>
On 26.02.2012 22:22, Keshav P R wrote:
> Coming to the issue of distro package, has the uefi relocator hang
> (seen in many asus laptops) been fixed in bzr mainline?
The reports feature one bug that debug=all caused relocator to hang. I
don't know what happens in case when no "debug" is set and whether it's
relocator's (or GRUB's at all for that matter) fault.
> On 27/02/2012, Keshav P R<the.ridikulus.rat@gmail.com> wrote:
>> I am asking about 'this' patch (patch 1/3) alone. Not the other two
>> ones. And the distro package was never updated, it was just a test
>> build with a bzr snapshot and these patches, given to users willing to
>> test the code.
>>
>> - Keshav
>>
>> On 27/02/2012, Vladimir 'φ-coder/phcoder' Serbinenko<phcoder@gmail.com>
>> wrote:
>>> On 26.02.2012 22:01, Keshav P R wrote:
>>>> Status of this patch in grub2 v2.00 code freeze?
>>> I have written what have to be fixed first.
>>> And one thing: your idea to put into distro a patch which has known
>>> serious issues that have to be resolved was a very bad one.
>>>
>>> --
>>> Regards
>>> Vladimir 'φ-coder/phcoder' Serbinenko
>>>
>>>
>>> _______________________________________________
>>> Grub-devel mailing list
>>> Grub-devel@gnu.org
>>> https://lists.gnu.org/mailman/listinfo/grub-devel
>>>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
next prev parent reply other threads:[~2012-02-26 21:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 16:55 [PATCH V3 1/3] Update the Linux boot protocol Matthew Garrett
2012-02-08 16:55 ` [PATCH V3 2/3] Add support for avoiding firmware in relocations Matthew Garrett
2012-02-08 19:41 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-02-08 22:22 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-02-08 22:25 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-02-08 16:55 ` [PATCH V3 3/3] Update Linux loader to follow the kernel's preferences Matthew Garrett
2012-02-08 19:49 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-02-08 19:35 ` [PATCH V3 1/3] Update the Linux boot protocol Vladimir 'φ-coder/phcoder' Serbinenko
2012-02-26 21:01 ` Keshav P R
2012-02-26 21:12 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-02-26 21:18 ` Keshav P R
2012-02-26 21:22 ` Keshav P R
2012-02-26 21:29 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-02-26 21:34 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4F4AA423.9020102@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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.