From: "Laszlo Ersek" <lersek@redhat.com>
To: vit9696 <vit9696@protonmail.com>,
"Rothman, Michael A" <michael.a.rothman@intel.com>,
Andrew Fish <afish@apple.com>
Cc: "Gao, Zhichao" <zhichao.gao@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Marvin Häuser" <mhaeuser@outlook.de>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Ni, Ray" <ray.ni@intel.com>
Subject: Re: [edk2-devel] [PATCH 1/1] ShellPkg: Add support for input with separately reported modifiers
Date: Fri, 24 Apr 2020 11:20:13 +0200 [thread overview]
Message-ID: <fe82e478-0366-a584-2dad-10bccbf6a19c@redhat.com> (raw)
In-Reply-To: <B50243DB-8F87-4417-B8D0-A4DEF60472B9@protonmail.com>
On 04/22/20 18:55, vit9696 wrote:
> In fact, there are really many mistakes in UEFI spec even besides
> this one, but we do not know where to report them. E.g. last thing we
> saw was ByRegisterNotify description in LocateHandleBuffer, which was
> mistakingly copy-pasted from LocateHandle.
Please join the UEFI forum:
https://uefi.org/membership
And then you get access to the Mantis bug tracker where you can file
tickets about UEFI spec issues.
(Most recently, I filed
<https://mantis.uefi.org/mantis/view.php?id=2095> just this Monday,
about some typos in the UEFI spec.)
Personally, I used the "Company Representative Sign Up" form, because
Red Hat had already been a "contributing member" company
<https://uefi.org/members>.
If your company doesn't want that kind of (paid) membership, I think you
-- plural -- could become an "adopter", or you -- singular -- could even
become an "individual adopter".
The page <https://uefi.org/members> lists a number of individual
adopters, so it's definitely a functional process. And I believe
individual adopters can access the Mantis bug tracker.
Michael and Andrew, please correct the above if necessary.
Thanks
Laszlo
prev parent reply other threads:[~2020-04-24 9:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 10:18 [PATCH 0/1] ShellPkg: Add support for input with separately reported modifiers Vitaly Cheptsov
2020-02-10 10:18 ` [PATCH 1/1] " Vitaly Cheptsov
2020-02-14 11:55 ` Vitaly Cheptsov
2020-02-19 6:55 ` [edk2-devel] " Gao, Zhichao
2020-02-19 12:15 ` Vitaly Cheptsov
2020-02-20 0:27 ` Gao, Zhichao
2020-03-27 11:00 ` Vitaly Cheptsov
2020-04-02 6:57 ` Gao, Zhichao
[not found] ` <1601EE5ED9DEC05E.18513@groups.io>
2020-04-02 8:28 ` Gao, Zhichao
2020-04-17 18:14 ` Vitaly Cheptsov
2020-04-22 1:55 ` Gao, Zhichao
2020-04-22 16:55 ` Vitaly Cheptsov
2020-04-24 9:20 ` 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=fe82e478-0366-a584-2dad-10bccbf6a19c@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