grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH 3/5] arm64: Remove "loaded" checking in the grub_cmd_devicetree of linux.c
Date: Thu, 07 May 2015 15:21:47 +0200	[thread overview]
Message-ID: <554B66EB.3030207@gmail.com> (raw)
In-Reply-To: <549317B4.6080606@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]

On 18.12.2014 19:06, Fu Wei wrote:
>        Reason: (1)we don't need the check, actually
>                (2)it is a prerequisite for multiboot support
> 
That one is problematic. Normally execution of any kernel-loading
commands like linux resets the boot context. Exceptions are drivemap,
sendkey, acpi and memory map commands, somewhat unfortunately. I'm on
the edge as to whether we should extend this behaviour to other commands.
> Signed-off-by: Fu Wei <fu.wei@linaro.org>
> Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>
> ---
>  grub-core/loader/arm64/linux.c | 7 -------
>  1 file changed, 7 deletions(-)
> 
> diff --git a/grub-core/loader/arm64/linux.c b/grub-core/loader/arm64/linux.c
> index 987f5b9..e9e9a29 100644
> --- a/grub-core/loader/arm64/linux.c
> +++ b/grub-core/loader/arm64/linux.c
> @@ -185,13 +185,6 @@ grub_cmd_devicetree (grub_command_t cmd __attribute__ ((unused)),
>    void *blob = NULL;
>    int size;
>  
> -  if (!loaded)
> -    {
> -      grub_error (GRUB_ERR_BAD_ARGUMENT,
> -		  N_("you need to load the kernel first"));
> -      return GRUB_ERR_BAD_OS;
> -    }
> -
>    if (argc != 1)
>      return grub_error (GRUB_ERR_BAD_ARGUMENT, N_("filename expected"));
>  
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]

      reply	other threads:[~2015-05-07 13:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-18 18:06 [PATCH 3/5] arm64: Remove "loaded" checking in the grub_cmd_devicetree of linux.c Fu Wei
2015-05-07 13:21 ` Vladimir 'φ-coder/phcoder' Serbinenko [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=554B66EB.3030207@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).