From: Leif Lindholm <leif.lindholm@linaro.org>
To: Evan Lloyd <Evan.Lloyd@arm.com>
Cc: Sami Mujawar <Sami.Mujawar@arm.com>, nd <nd@arm.com>,
Arvind Chauhan <Arvind.Chauhan@arm.com>,
"ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Stephanie Hughes-Fitt <Stephanie.Hughes-Fitt@arm.com>
Subject: Re: [PATCH edk2-platforms v1 3/3][platforms/devel-dynamictables] Update Readme.md to reflect ACPICA compiler update
Date: Sat, 12 May 2018 12:25:38 +0100 [thread overview]
Message-ID: <20180512112538.lx36mbhr4xyl2uqb@bivouac.eciton.net> (raw)
In-Reply-To: <DB6PR08MB2806988D8A76424521A015D48B9F0@DB6PR08MB2806.eurprd08.prod.outlook.com>
On Fri, May 11, 2018 at 01:29:47PM +0000, Evan Lloyd wrote:
>
>
> > -----Original Message-----
> > From: edk2-devel <edk2-devel-bounces@lists.01.org> On Behalf Of Leif
> > Lindholm
> > Sent: 09 May 2018 12:04
> > To: Sami Mujawar <Sami.Mujawar@arm.com>
> > Cc: nd <nd@arm.com>; Arvind Chauhan <Arvind.Chauhan@arm.com>;
> > ard.biesheuvel@linaro.org; edk2-devel@lists.01.org; Stephanie Hughes-Fitt
> > <Stephanie.Hughes-Fitt@arm.com>
> > Subject: Re: [edk2] [PATCH edk2-platforms v1 3/3][platforms/devel-
> > dynamictables] Update Readme.md to reflect ACPICA compiler update
> >
> ...
> > > -A patch ***'Modify hex AML C header file generation'***, to enable
> > > -this support has been submitted to the ACPICA source repository.
> > > -<https://lists.acpica.org/pipermail/devel/2018-March/001755.html>
> > > +A patch ***'[iASL: Enhance the -tc option (create AML hex file in
> > >
> > +C)](https://github.com/acpica/acpica/commit/f9a88a4c1cd020b6a5475d63
> > b
> > > +29626852a0b5f37)'***, to enable this support has been integrated to
> > > +the ACPICA source repository.
> >
> > Linux distributions tend to use dates to refer to what particular point a
> > version is based on, since snapshot updates are frequently
> > necessary.
>
> [[Evan Lloyd]] Whilst agreeing that a date would be helpful, I don't
> think that Linux usage is relevant. EDK II seems to go to some
> lengths to avoid Linux usage (e.g. CR LF).
Linux distributions are consumers of edk2 code in the form of
packaged builds of ArmVirtPkg and OvmfPkg.
> > In this case, that is 16 March 2018 - please mention that as well in the
> > message.
> [[Evan Lloyd]] Given the international nature of edk2-devel, I
> suggest there is a strong case for adopting ISO-8601 date format, so
> I'd prefer 2018-03-16.
Yes please.
/
Leif
prev parent reply other threads:[~2018-05-12 11:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 14:58 [PATCH edk2-platforms v1 0/3][platforms/devel-dynamictables] Update for ACPICA compiler enhancements Sami Mujawar
2018-04-27 14:58 ` [PATCH edk2-platforms v1 1/3][platforms/devel-dynamictables] Platform/ARM: Match asl compiler output for Juno Sami Mujawar
2018-05-09 11:07 ` Leif Lindholm
2018-04-27 14:58 ` [PATCH edk2-platforms v1 2/3][platforms/devel-dynamictables] Platform/ARM: Match asl compiler output for FVP Sami Mujawar
2018-04-27 14:58 ` [PATCH edk2-platforms v1 3/3][platforms/devel-dynamictables] Update Readme.md to reflect ACPICA compiler update Sami Mujawar
2018-05-09 11:04 ` Leif Lindholm
2018-05-11 13:29 ` Evan Lloyd
2018-05-12 11:25 ` Leif Lindholm [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=20180512112538.lx36mbhr4xyl2uqb@bivouac.eciton.net \
--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