From: Laszlo Ersek <lersek@redhat.com>
To: Supreeth Venkatesh <supreeth.venkatesh@arm.com>, edk2-devel@lists.01.org
Cc: jonathan.zhang@cavium.com, liming.gao@intel.com,
leif.lindholm@linaro.org, felixp@ami.com,
michael.d.kinney@intel.com, jbrasen@qti.qualcomm.com
Subject: Re: [PATCH v4 00/10] *** BaseTools: Tools change to support MM Interface in PI v1.5 Specification ***
Date: Fri, 23 Jun 2017 23:19:20 +0200 [thread overview]
Message-ID: <f1d1715d-a0e7-1765-5360-d9cf393b60ef@redhat.com> (raw)
In-Reply-To: <1498250516-47996-1-git-send-email-supreeth.venkatesh@arm.com>
Hi,
On 06/23/17 22:41, Supreeth Venkatesh wrote:
> ***
> PI v1.5 Specification Volume 4 defines Management Mode Core Interface.
> In order to support Management Mode Core Interface, Module Types MM_STANDALONE, MM_CORE_STANDALONE are needed.
> PI specification v1.5 defines the following new file types:
> #define EFI_FV_FILETYPE_MM_STANDALONE 0x0E
> #define EFI_FV_FILETYPE_MM_CORE_STANDALONE 0x0F
> The following changes are necessitated in order to support the above changes to the specification.
>
> Changes Since v3:
> (*) Update Review Comments from Liming, Felix.
> (*) Directly define FV file types MM_STANDALONE / MM_CORE_STANDALONE
> and module types MM_STANDALONE / MM_CORE_STANDALONE
> i.e., with MM prefix instead of SMM prefix.
>
> Changes Since v2:
> Add missing EFI_FV_FILETYPE_MM_CORE_STANDALONE defined in PI Specification v1.5 VOL3,
> but not defined in VOL4.
>
> Changes Since v1:
> Corrected Version check HEX Value "0x00010032" (1 and 50), not 0x0001000A (1 and 10)
> ***
I have a generic comment for this series (sorry that I'm making it this
late; I'm somewhat surprised that others haven't pointed out the same yet):
Every patch in the series has the exact same subject:
BaseTools: Tools change to support PI v1.5 Specification.
Unfortunately, that's useless. The commit message *bodies* look great
and thoughtful, but the subject lines convey zero meaning.
Please replace every subject with a meaningful summary of the larger
commit message, such that the subject line still fits in 74 characters
or so. For example, for the first two patches:
BaseTools/GenFfs: add FFS file types for management mode modules
BaseTools/GenFw: recognize MM file types as EFI Boot Service Drivers
and so on.
Thanks,
Laszlo
next prev parent reply other threads:[~2017-06-23 21:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 20:41 [PATCH v4 00/10] *** BaseTools: Tools change to support MM Interface in PI v1.5 Specification *** Supreeth Venkatesh
2017-06-23 20:41 ` [PATCH v4 01/10] BaseTools: Tools change to support PI v1.5 Specification Supreeth Venkatesh
2017-06-23 20:41 ` [PATCH v4 02/10] " Supreeth Venkatesh
2017-06-23 20:41 ` [PATCH v4 03/10] " Supreeth Venkatesh
2017-06-23 20:41 ` [PATCH v4 04/10] " Supreeth Venkatesh
2017-06-23 20:41 ` [PATCH v4 05/10] " Supreeth Venkatesh
2017-06-23 20:41 ` [PATCH v4 06/10] " Supreeth Venkatesh
2017-06-23 20:41 ` [PATCH v4 07/10] " Supreeth Venkatesh
2017-06-23 20:41 ` [PATCH v4 08/10] " Supreeth Venkatesh
2017-06-23 20:41 ` [PATCH v4 09/10] " Supreeth Venkatesh
2017-06-23 20:41 ` [PATCH v4 10/10] " Supreeth Venkatesh
2017-06-23 21:19 ` Laszlo Ersek [this message]
2017-06-26 16:15 ` [PATCH v4 00/10] *** BaseTools: Tools change to support MM Interface in PI v1.5 Specification *** Supreeth Venkatesh
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=f1d1715d-a0e7-1765-5360-d9cf393b60ef@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