From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Matthew Garrett <matthewgarrett@google.com>
Cc: linux-integrity@vger.kernel.org, peterhuewe@gmx.de, jgg@ziepe.ca,
linux-efi@vger.kernel.org, ard.biesheuvel@linaro.org,
Matthew Garrett <mjg59@google.com>
Subject: Re: [PATCH] efi: Fix TPM code build failure on ARM
Date: Sun, 9 Jun 2019 22:53:37 +0300 [thread overview]
Message-ID: <20190609195337.GA25074@linux.intel.com> (raw)
In-Reply-To: <20190605181140.35559-1-matthewgarrett@google.com>
On Wed, Jun 05, 2019 at 11:11:40AM -0700, Matthew Garrett wrote:
> asm/early_ioremap.h needs to be #included before tpm_eventlog.h in order
> to ensure that early_memremap is available.
>
> Signed-off-by: Matthew Garrett <mjg59@google.com>
Thanks, squashed to "tpm: Reserve the TPM final events table".
/Jarkko
prev parent reply other threads:[~2019-06-09 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 18:11 [PATCH] efi: Fix TPM code build failure on ARM Matthew Garrett
2019-06-06 11:39 ` Ard Biesheuvel
2019-06-06 16:03 ` Matthew Garrett
2019-06-07 10:03 ` Ard Biesheuvel
2019-06-09 19:53 ` Jarkko Sakkinen [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-all 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=20190609195337.GA25074@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=ard.biesheuvel@linaro.org \
--cc=jgg@ziepe.ca \
--cc=linux-efi@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=matthewgarrett@google.com \
--cc=mjg59@google.com \
--cc=peterhuewe@gmx.de \
/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;
as well as URLs for NNTP newsgroup(s).