From: Matt Fleming <matt@codeblueprint.co.uk>
To: Tom Yan <tom.ty89@gmail.com>
Cc: Josh Triplett <josh@joshtriplett.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
linux-efi@vger.kernel.org, linux-acpi@vger.kernel.org,
Matt Fleming <matt.fleming@intel.com>
Subject: Re: [PATCH] x86/efi-bgrt: Switch pr_err() to pr_debug() for invalid BGRT
Date: Tue, 30 Jun 2015 11:00:46 +0100 [thread overview]
Message-ID: <20150630100046.GI28334@codeblueprint.co.uk> (raw)
In-Reply-To: <CAGnHSEnO9BiCTgSOCJnJiwycpSMKtQzeYb1+S-2Cq7U_Xy+H1w@mail.gmail.com>
On Tue, 30 Jun, at 05:52:43AM, Tom Yan wrote:
> Hi Matt!
>
> The patch works for me against linux 4.0.6. I no longer see the
> message in dmesg with the BIOS option set to "Auto". I assume this is
> expected? It will only be displayed if I build it with a debug flag,
> right?
> https://www.kernel.org/doc/local/pr_debug.txt
Right, that is the expected outcome but it's always good to check that I
didn't somehow goof up the patch.
Thanks for testing!
--
Matt Fleming, Intel Open Source Technology Center
prev parent reply other threads:[~2015-06-30 10:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 12:06 [PATCH] x86/efi-bgrt: Switch pr_err() to pr_debug() for invalid BGRT Matt Fleming
[not found] ` <1435579602-6612-1-git-send-email-matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-06-29 13:13 ` Borislav Petkov
[not found] ` <20150629131305.GB13113-fF5Pk5pvG8Y@public.gmane.org>
2015-06-29 14:00 ` Josh Triplett
2015-06-29 14:17 ` Borislav Petkov
[not found] ` <20150629141724.GG12383-fF5Pk5pvG8Y@public.gmane.org>
2015-06-29 14:45 ` josh-iaAMLnmF4UmaiuxdJuQwMA
2015-06-29 14:49 ` Matt Fleming
[not found] ` <20150629144940.GF28334-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-06-29 14:53 ` josh-iaAMLnmF4UmaiuxdJuQwMA
2015-06-29 15:44 ` Borislav Petkov
2015-06-29 16:35 ` josh
2015-06-30 9:31 ` Matt Fleming
2015-06-29 14:02 ` Josh Triplett
2015-06-29 21:52 ` Tom Yan
2015-06-30 10:00 ` 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=20150630100046.GI28334@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=josh@joshtriplett.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mjg59@srcf.ucam.org \
--cc=tom.ty89@gmail.com \
/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.