From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: "Yao, Jiewen" <jiewen.yao@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Gao, Liming" <liming.gao@intel.com>,
"leif.lindholm@linaro.org" <leif.lindholm@linaro.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [PATCH] MdePkg/Uefi: pack EFI_CAPSULE_TABLE struct
Date: Fri, 3 Mar 2017 13:45:38 +0000 [thread overview]
Message-ID: <CAKv+Gu_ZMcP6t5V=E7QNgg7P8xUvsXSOMzyWrW9n+UN+RZEj_A@mail.gmail.com> (raw)
In-Reply-To: <74D8A39837DF1E4DA445A8C0B3885C503A8F901F@shsmsx102.ccr.corp.intel.com>
On 3 March 2017 at 13:24, Yao, Jiewen <jiewen.yao@intel.com> wrote:
> HI Ard
> Thanks to raise this issue.
>
> I agree with you on pack.
>
> I think there is still some confusing in " The EFI System Table entry must point to an array of capsules that contain the same CapsuleGuid value."
>
> I am still not clear if it is a proper way to use "an array of capsule headers" to represent the "an array of capsules".
>
> I recommend we ask USWG to clarify the meaning to avoid misunderstanding.
>
Yes, please.
prev parent reply other threads:[~2017-03-03 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 12:16 [PATCH] MdePkg/Uefi: pack EFI_CAPSULE_TABLE struct Ard Biesheuvel
2017-03-03 13:24 ` Yao, Jiewen
2017-03-03 13:45 ` 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+Gu_ZMcP6t5V=E7QNgg7P8xUvsXSOMzyWrW9n+UN+RZEj_A@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