From: "Môshe van der Sterre" <me-A/3C56C7qwM@public.gmane.org>
To: Josh Triplett <josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org>
Cc: Matt Fleming
<matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>,
Andy Lutomirski <luto-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: BGRT warns again on my system
Date: Sun, 19 Jun 2016 16:57:17 +0200 [thread overview]
Message-ID: <5766B2CD.6010401@moshe.nl> (raw)
In-Reply-To: <20160619143840.GA18605@x>
On 06/19/2016 04:38 PM, Josh Triplett wrote:
> On Sun, Jun 19, 2016 at 03:14:40PM +0200, Môshe van der Sterre wrote:
>> On 06/02/2016 11:24 AM, Matt Fleming wrote:
>>
>>> If this does indeed fix Andy's immediate issue (and it looks like
>>> it would) I'm happy to apply this as an interim solution.
>> I have tested that this does indeed fix the warning for Andy's value of
>> ->image_address, but off course I can't test this with the actual hardware
>> that Andy has. Do you want me to resend this with a commit message so it can
>> be applied?
> With a commit message and a clearer pr_notice than "is bogus", yes. How
> about "image address not a valid physical memory address"?
The sub-par notice text crossed my mind when I originally mailed it, but
I forgot about it today. I like your suggestion so I'll use that one.
next prev parent reply other threads:[~2016-06-19 14:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-28 20:46 BGRT warns again on my system Andy Lutomirski
[not found] ` <CALCETrUJ2QoUSYY82Q1BN3niasiunktnrmdE9Lmi2PZnCJRdag-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-05-28 22:25 ` Josh Triplett
2016-05-29 4:09 ` Môshe van der Sterre
[not found] ` <574A6B5D.60200-A/3C56C7qwM@public.gmane.org>
2016-06-02 9:24 ` Matt Fleming
[not found] ` <20160602092438.GD2658-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-06-19 13:14 ` Môshe van der Sterre
[not found] ` <57669AC0.7010905-A/3C56C7qwM@public.gmane.org>
2016-06-19 14:38 ` Josh Triplett
2016-06-19 14:57 ` Môshe van der Sterre [this message]
2016-06-20 5:38 ` Dave Young
[not found] ` <20160620053819.GB13633-0VdLhd/A9Pl+NNSt+8eSiB/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2016-06-20 15:50 ` Josh Triplett
2016-06-23 12:01 ` Matt Fleming
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=5766B2CD.6010401@moshe.nl \
--to=me-a/3c56c7qwm@public.gmane.org \
--cc=josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=luto-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@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 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.