From: Sunil V L <sunilvl@ventanamicro.com>
To: RISC-V SW Dev <sw-dev@groups.riscv.org>,
tech-unixplatformspec <tech-unixplatformspec@lists.riscv.org>,
isa-dev@groups.riscv.org, linux-riscv@lists.infradead.org
Subject: Public review of RISC-V UEFI Protocol Specification
Date: Wed, 23 Mar 2022 21:46:04 +0530 [thread overview]
Message-ID: <20220323161604.GA54531@sunil-laptop> (raw)
This is to announce the start of the public review period for
the RISC-V UEFI Protocol specification. This specification is
considered as frozen now as per the RISC-V International policies.
The review period begins today, Wednesday March 23, and ends on Friday
May 6 (inclusive).
The specification can be found here
https://github.com/riscv-non-isa/riscv-uefi/releases/download/1.0-rc3/RISCV_UEFI_PROTOCOL-spec.pdf
which was generated from the source available in the following GitHub
repo:
https://github.com/riscv-non-isa/riscv-uefi
The specification is also attached in this email.
To respond to the public review, please either reply to this email or
send comments to the platform mailing list[1] or add issues to the
GitHub repo[2]. We welcome all input and appreciate your time and
effort in helping us by reviewing the specification.
During the public review period, corrections, comments, and
suggestions, will be gathered for review by the Platform HSC members.
Any minor corrections and/or uncontroversial changes will be
incorporated into the specification. Any remaining issues or proposed changes
will be addressed in the public review summary report. If there are no
issues that require incompatible changes to the public review
specification, the platform HSC will recommend the updated
specifications be approved and ratified by the RISC-V Technical
Steering Committee and the RISC-V Board of Directors.
Thanks to all the contributors for all their hard work.
[1] tech-unixplatformspec@lists.riscv.org
[2] https://github.com/riscv-non-isa/riscv-uefi/issues
Regards
Sunil
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2022-03-23 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 16:16 Sunil V L [this message]
2022-03-23 16:25 ` [RISC-V] [tech-unixplatformspec] Public review of RISC-V UEFI Protocol Specification Anup Patel
2022-03-23 17:00 ` [PATCH] Fix typos in introduction for RISCV_EFI_BOOT_PROTOCOL Heinrich Schuchardt
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=20220323161604.GA54531@sunil-laptop \
--to=sunilvl@ventanamicro.com \
--cc=isa-dev@groups.riscv.org \
--cc=linux-riscv@lists.infradead.org \
--cc=sw-dev@groups.riscv.org \
--cc=tech-unixplatformspec@lists.riscv.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox