From: Matt Fleming <matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
To: Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>
Cc: Matt Fleming
<matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Leif Lindholm <Leif.Lindholm-5wv7dgnIgG8@public.gmane.org>
Subject: Re: [PATCH] efi: fdt: Do not report an error during boot if UEFI is not available
Date: Thu, 10 Jul 2014 11:04:26 +0100 [thread overview]
Message-ID: <20140710100426.GD15932@console-pimps.org> (raw)
In-Reply-To: <1404834858-10706-1-git-send-email-catalin.marinas-5wv7dgnIgG8@public.gmane.org>
On Tue, 08 Jul, at 04:54:18PM, Catalin Marinas wrote:
> Currently, fdt_find_uefi_params() reports an error if no EFI parameters
> are found in the DT. This is however a valid case for non-UEFI kernel
> booting. This patch checks changes the error reporting to a
> pr_info("UEFI not found") when no EFI parameters are found in the DT.
>
> Signed-off-by: Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>
> Acked-by: Leif Lindholm <leif.lindholm-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> Tested-by: Leif Lindholm <leif.lindholm-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> ---
> drivers/firmware/efi/efi.c | 22 +++++++++++++++-------
> 1 file changed, 15 insertions(+), 7 deletions(-)
Thanks, applied to 'urgent' for v3.16.
--
Matt Fleming, Intel Open Source Technology Center
prev parent reply other threads:[~2014-07-10 10:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 15:54 [PATCH] efi: fdt: Do not report an error during boot if UEFI is not available Catalin Marinas
[not found] ` <1404834858-10706-1-git-send-email-catalin.marinas-5wv7dgnIgG8@public.gmane.org>
2014-07-10 10:04 ` Matt Fleming [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=20140710100426.GD15932@console-pimps.org \
--to=matt-hnk1s37rvnbexh+ff434mdi2o/jbrioy@public.gmane.org \
--cc=Leif.Lindholm-5wv7dgnIgG8@public.gmane.org \
--cc=catalin.marinas-5wv7dgnIgG8@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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).