From: Laszlo Ersek <lersek@redhat.com>
To: marcandre.lureau@redhat.com, edk2-devel@lists.01.org
Cc: qemu-devel@nongnu.org, javierm@redhat.com, pjones@redhat.com,
jiewen.yao@intel.com
Subject: Re: [PATCH 0/4] RFC: ovmf: Add support for TPM Physical Presence interface
Date: Wed, 16 May 2018 11:29:24 +0200 [thread overview]
Message-ID: <229d0059-2ab4-bf2d-cbf5-9dca4ff978bd@redhat.com> (raw)
In-Reply-To: <20180515123007.10164-1-marcandre.lureau@redhat.com>
Hi Marc-André,
On 05/15/18 14:30, marcandre.lureau@redhat.com wrote:
> From: Marc-André Lureau <marcandre.lureau@redhat.com>
>
> Hi,
>
> The following series adds basic TPM PPI 1.3 support for OVMF-on-QEMU
> with TPM2 (I haven't tested TPM1, for lack of interest).
I got the review of this patch series added to my TODO list, but I'll
have to ask for your patience. :(
>From an extremely superficial skim:
* please use the
TopDirPkg/ModuleName: blah blah blah
subject format, or more generally, if a module cannot be identified,
TopDirPkg: blah blah blah
* the subject line and the commit message shouldn't be wider than 74
chars;
* edk2 uses two spaces for general indentation, and I'm noticing some
inconsistency there (4 spaces like in QEMU).
* Please consider formatting the patches with "--find-copies-harder"
(although I can look at them with the same option after fetching the
series from your repo). This option is usually helpful for reviewers
when cloning and modifying modules cross-package.
* Please consider adopting the git settings at
<https://github.com/tianocore/tianocore.github.io/wiki/Laszlo's-unkempt-git-guide-for-edk2-contributors-and-maintainers>,
in particular:
- "--stat=1000 --stat-graph-width=20", so that pathnames are not
truncated in the diffstats,
- the "xfuncname"-related settings, so that git diff hunk headers @@
are useful for DSC and INF files too,
- the diff order file, so that files are listed in patches in logical
order, going from abstract / descriptive (.inf, .h) to concrete /
imperative (.c).
Not much of a review, I know; this is all I can offer right now. If you
have the time to respin just with these superficial changes, that might
make my life easier. If you prefer to delay them, that's 100% fine too.
Thanks
Laszlo
next prev parent reply other threads:[~2018-05-16 9:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 12:30 [PATCH 0/4] RFC: ovmf: Add support for TPM Physical Presence interface marcandre.lureau
2018-05-15 12:30 ` [PATCH 1/4] ovmf: add and link with Tcg2PhysicalPresenceLibNull when !TPM2_ENABLE marcandre.lureau
2018-05-17 7:58 ` Laszlo Ersek
2018-05-15 12:30 ` [PATCH 2/4] ovmf: add QemuTpm.h header marcandre.lureau
2018-05-17 8:10 ` Laszlo Ersek
2018-05-15 12:30 ` [PATCH 3/4] ovmf: replace SecurityPkg with OvfmPkg Tcg2PhysicalPresenceLibQemu marcandre.lureau
2018-05-17 10:14 ` Laszlo Ersek
2018-05-15 12:30 ` [PATCH 4/4] ovmf: process TPM PPI request in AfterConsole() marcandre.lureau
2018-05-17 10:24 ` Laszlo Ersek
2018-05-16 9:29 ` Laszlo Ersek [this message]
2018-05-17 7:41 ` [PATCH 0/4] RFC: ovmf: Add support for TPM Physical Presence interface Laszlo Ersek
2018-05-17 14:43 ` Marc-André Lureau
2018-05-17 14:58 ` Laszlo Ersek
2018-05-17 7:54 ` Laszlo Ersek
2018-05-17 8:26 ` Laszlo Ersek
2018-05-17 14:44 ` Marc-André Lureau
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=229d0059-2ab4-bf2d-cbf5-9dca4ff978bd@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