From: Andrew Fish <afish@apple.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@ml01.01.org>
Subject: Re: [PATCH] UefiCpuPkg/SecCore: Use %x to print stack information
Date: Tue, 15 Nov 2016 10:33:27 -0800 [thread overview]
Message-ID: <5E3F55DD-E1B7-4159-B026-FFF56D6EAAFA@apple.com> (raw)
In-Reply-To: <4804ad49-f8d9-90d5-21f5-7b44d2229b95@redhat.com>
> On Nov 15, 2016, at 10:11 AM, Laszlo Ersek <lersek@redhat.com> wrote:
>
> [edk2] What is the right way to print a UINTN?
>
> https://lists.01.org/pipermail/edk2-devel/2016-September/002091.html <https://lists.01.org/pipermail/edk2-devel/2016-September/002091.html>
>
> (There seem to be issues with my focus / attention recently... This is
> now the second near-trivial issue I've missed in a couple of days. :( I
> guess I should get more sleep.)
Laszlo,
No worries that is why more eye balls is better.
There is a lot of scientific work on mental/information overload and pilots. https://www.ucl.ac.uk/news/news-articles/170314-Information-overload-dims-our-lights
Thanks,
Andrew Fish
next prev parent reply other threads:[~2016-11-15 18:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 8:32 [PATCH] UefiCpuPkg/SecCore: Use %x to print stack information Jeff Fan
2016-11-15 8:37 ` Tian, Feng
2016-11-15 16:59 ` Laszlo Ersek
2016-11-15 17:47 ` Andrew Fish
2016-11-15 18:11 ` Laszlo Ersek
2016-11-15 18:33 ` Andrew Fish [this message]
2016-11-16 1:01 ` Fan, Jeff
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-list 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=5E3F55DD-E1B7-4159-B026-FFF56D6EAAFA@apple.com \
--to=devel@edk2.groups.io \
/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