From: Laszlo Ersek <lersek@redhat.com>
To: Philipp Deppenwiese <zaolin.daisuki@gmail.com>
Cc: edk2-devel@lists.01.org
Subject: Re: [OvmfPkg] Secure Boot issues
Date: Mon, 18 Jun 2018 14:30:19 +0200 [thread overview]
Message-ID: <a3b23947-a12d-699c-c1eb-e0c81893a807@redhat.com> (raw)
In-Reply-To: <5061cc63-73f7-95c3-be94-6a774bebf5cf@gmail.com>
On 06/18/18 14:14, Philipp Deppenwiese wrote:
> Hey Laszlo,
>
> We guess that's an issue on our side because of some
> NVRAM issues with VirtualBox. We located it through Windows 10
> debugging.
Good job! :)
> Thanks a lot for your support and testing!
>
> Maybe you are interested to join the www.osfc.io
> and talk about some OVMF details. :)
Due to family circumstances, I travel once per year at most, and that's
usually to the KVM Forum (whenever I can manage).
If a conference is brought to Budapest, Hungary, there's a much better
chance I can drop by on a daily basis. (Linaro Connect 2017 was like
this, and it was fantastic.)
I don't do public speaking, as a rule. At the KVM Fora, I attempt to
participate in BoF / round-table discussions about OVMF. These have been
very small historically, and on the scale that's still approachable to me.
Thanks!
Laszlo
prev parent reply other threads:[~2018-06-18 12:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 13:12 [OvmfPkg] Secure Boot issues Philipp Deppenwiese
2018-06-12 13:59 ` Laszlo Ersek
2018-06-12 14:51 ` Philipp Deppenwiese
2018-06-12 18:14 ` Laszlo Ersek
2018-06-13 13:45 ` Philipp Deppenwiese
2018-06-13 19:21 ` Laszlo Ersek
2018-06-13 19:41 ` Philipp Deppenwiese
2018-06-13 21:18 ` Laszlo Ersek
2018-06-13 21:25 ` Philipp Deppenwiese
2018-06-14 17:29 ` Laszlo Ersek
2018-06-18 12:14 ` Philipp Deppenwiese
2018-06-18 12:30 ` Laszlo Ersek [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-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=a3b23947-a12d-699c-c1eb-e0c81893a807@redhat.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