From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Matthew Garrett <mjg59@google.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
jmorris@namei.org
Subject: Re: linux-next: build failure after merge of the tpmdd tree
Date: Tue, 30 Apr 2019 17:47:27 +0300 [thread overview]
Message-ID: <20190430144727.GA7901@linux.intel.com> (raw)
In-Reply-To: <CACdnJuvat4=kXD6NMnMw5E8M4KB_1nBP6Simi8gBUChdBs7eRw@mail.gmail.com>
On Thu, Apr 18, 2019 at 12:40:48PM -0700, Matthew Garrett wrote:
> On Tue, Apr 16, 2019 at 8:36 AM Jarkko Sakkinen
> <jarkko.sakkinen@linux.intel.com> wrote:
> > Matthew, looking at the code I guess the includes are in wrong order
> > i.e. early_ioremap.h should be included before tpm_eventlog.h. Do you
> > agree that this is the correct conclusion? I can do the update.
>
> Yes, I believe that that's the correct fix.
I'll hold up until the previous flush of patches is in
security/next-general (bug fixes for v5.1 changes).
/Jarkko
next prev parent reply other threads:[~2019-04-30 14:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 3:07 linux-next: build failure after merge of the tpmdd tree Stephen Rothwell
2019-04-16 15:36 ` Jarkko Sakkinen
2019-04-18 19:40 ` Matthew Garrett
2019-04-30 14:47 ` Jarkko Sakkinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-27 12:55 broonie
2023-04-27 19:06 ` Jarkko Sakkinen
2023-03-21 0:54 Stephen Rothwell
2023-03-24 2:20 ` Stephen Rothwell
2023-03-29 22:05 ` Jarkko Sakkinen
2023-03-29 22:03 ` Jarkko Sakkinen
2019-06-05 2:09 Stephen Rothwell
2019-06-05 14:52 ` Jarkko Sakkinen
2017-05-10 3:23 Stephen Rothwell
2017-05-10 12:51 ` Jarkko Sakkinen
2016-04-28 5:32 Stephen Rothwell
2016-04-28 9:02 ` Jarkko Sakkinen
2016-05-01 13:12 ` Stephen Rothwell
2016-05-02 11:10 ` Jarkko Sakkinen
2016-05-02 12:19 ` Stephen Rothwell
2016-05-02 16:26 ` Jarkko Sakkinen
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=20190430144727.GA7901@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mjg59@google.com \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.