From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: Gaurav Jain <gaurav.jain@nxp.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
Leif Lindholm <leif@nuviainc.com>,
Pankaj Bansal <pankaj.bansal@nxp.com>
Subject: Re: FW: [EXT] Re: [PATCH 1/1] EmbeddedPkg: Fixed Asserts in SCT Runtime Services test.
Date: Mon, 17 Feb 2020 08:02:01 +0100 [thread overview]
Message-ID: <CAKv+Gu9NXHYikOvn88WLyFpd9+ERMhcM1EbR-xSygUZJmR6TDA@mail.gmail.com> (raw)
In-Reply-To: <CAKv+Gu_zmkwGvyFmVNj4pwwUD8X=G3DgN2pJUq=mu-79kFko_w@mail.gmail.com>
On Mon, 17 Feb 2020 at 07:56, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
>
> On Mon, 17 Feb 2020 at 07:25, Gaurav Jain <gaurav.jain@nxp.com> wrote:
> >
> > Hi Ard
> >
> > I have also checked UEFI Shell Specification Version 2.2(https://uefi.org/sites/default/files/resources/UEFI_Shell_2_2.pdf)
> > For date command the range of valid years is from 1998–2099 (on page 121)
> >
> > So Range of valid years is conflicting in UEFI Spec and UEFI Shell Spec.
> > I think UEFI spec needs to be corrected. What are your thoughts?
> >
>
> Page 121 does not mention data. Page 111 does, and tells me that a
> two-digit year is interpreted as 199x or 20xx, and a four digit year
> is interpreted as is.
>
> How exactly does that conflict with the UEFI spec?
>
OK, so I found this on page 111:
"""The range of valid years is from 1998–2099"""
and so indeed, the Shell 'date' command's year range is narrower than
the UEFI spec's, but that does not make it non-compliant.
prev parent reply other threads:[~2020-02-17 7:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 5:08 [PATCH 1/1] EmbeddedPkg: Fixed Asserts in SCT Runtime Services test Gaurav Jain
2020-01-30 9:21 ` Ard Biesheuvel
2020-01-31 8:27 ` [EXT] " gaurav.jain
2020-02-11 10:37 ` FW: " Gaurav Jain
2020-02-11 14:19 ` Ard Biesheuvel
2020-02-17 6:25 ` Gaurav Jain
2020-02-17 6:56 ` Ard Biesheuvel
2020-02-17 7:02 ` Ard Biesheuvel [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=CAKv+Gu9NXHYikOvn88WLyFpd9+ERMhcM1EbR-xSygUZJmR6TDA@mail.gmail.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