From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
linux-integrity@vger.kernel.org
Subject: Re: [PATCH v3] tpm: fix intermittent failure with self tests
Date: Tue, 20 Feb 2018 12:51:51 -0500 [thread overview]
Message-ID: <1519149111.4446.11.camel@HansenPartnership.com> (raw)
In-Reply-To: <1519148635.6941.5.camel@linux.intel.com>
On Tue, 2018-02-20 at 19:43 +0200, Jarkko Sakkinen wrote:
> I get merge conflicts in my tree but I'll review this.
You told me to rebase it on that patch that wasn't in your tree:
https://patchwork.kernel.org/patch/10208965/
If you put it in your tree, I can just rebase on top of everything.
James
next prev parent reply other threads:[~2018-02-20 17:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 12:24 [PATCH v3] tpm: fix intermittent failure with self tests James Bottomley
2018-02-20 17:43 ` Jarkko Sakkinen
2018-02-20 17:51 ` James Bottomley [this message]
2018-02-20 19:26 ` Jarkko Sakkinen
2018-02-20 21:27 ` Jarkko Sakkinen
2018-02-20 21:28 ` Jarkko Sakkinen
2018-02-20 21:29 ` Jarkko Sakkinen
2018-02-20 23:09 ` James Bottomley
2018-02-21 7:25 ` Jarkko Sakkinen
2018-02-21 7:42 ` Paul Menzel
2018-02-21 13:36 ` Jarkko Sakkinen
2018-02-21 7:04 ` Paul Menzel
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=1519149111.4446.11.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-integrity@vger.kernel.org \
/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