From: James Morris <jmorris@namei.org>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, tpmdd-devel@lists.sourceforge.net
Subject: Re: [GIT PULL] tpmdd fixes for 4.12
Date: Tue, 25 Apr 2017 10:04:20 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1704251004100.8213@namei.org> (raw)
In-Reply-To: <20170424213710.qrc5za4tigjdqspi@intel.com>
On Tue, 25 Apr 2017, Jarkko Sakkinen wrote:
> Hi
>
> Here are fixes for the 4.12 release. In addition there is an update to
> the tpm_tis driver to use common callbacks for requesting and
> relinquishing locality as they were with locality support for tpm_crb.
> Now the logic flow for both driver is driven in tpm_transmit().
>
pulled, thanks!
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2017-04-25 0:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 21:37 [GIT PULL] tpmdd fixes for 4.12 Jarkko Sakkinen
2017-04-24 21:39 ` Jarkko Sakkinen
2017-04-25 0:04 ` James Morris [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=alpine.LRH.2.20.1704251004100.8213@namei.org \
--to=jmorris@namei.org \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).