From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: James Morris <jmorris@namei.org>
Cc: linux-security-module@vger.kernel.org, keyrings@vger.kernel.org,
linux-kernel@vger.kernel.org, tpmdd-devel@lists.sourceforge.net
Subject: Re: [GIT PULL] tpmdd fixes for Linux 4.5
Date: Mon, 8 Feb 2016 22:46:10 +0200 [thread overview]
Message-ID: <20160208204610.GA14626@intel.com> (raw)
In-Reply-To: <20160119233903.GA12337@intel.com>
James,
On Wed, Jan 20, 2016 at 01:39:03AM +0200, Jarkko Sakkinen wrote:
> Hi James,
>
> This pull request contains three small cleanups, a bug fix for policy
> based sealing, a bug fix for attach/detach of the platform device for
> tpm_tis and resource locking for tpm_tis and tpm_crb.
I have 3-4 small scope fixes for the release that have been implemented
after this.
Since it's bee a while since this pull request should I create a new one
and include those or do you want to pull this first?
I could rebase that new pull request to -rc3 to which security/next is
now rebased.
Thanks.
/Jarkko
> /Jarkko
>
> The following changes since commit 607259e17b37017e9ec0249a8b0a7d8b76b572aa:
>
> Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity into ra-next (2016-01-10 21:52:17 +1100)
>
> are available in the git repository at:
>
> https://github.com/jsakkine/linux-tpmdd.git tags/tpmdd-next-20160120
>
> for you to fetch changes up to bb76f9ba498881ed57444fa2a7b5aafd66c207ba:
>
> tpm_crb: Use devm_ioremap_resource (2016-01-20 01:28:51 +0200)
>
> ----------------------------------------------------------------
> tpmdd fixes for Linux 4.5
>
> ----------------------------------------------------------------
> Jarkko Sakkinen (1):
> tpm: fix checks for policy digest existence in tpm2_seal_trusted()
>
> Jason Gunthorpe (7):
> tpm_crb: Use the common ACPI definition of struct acpi_tpm2
> tpm_tis: Disable interrupt auto probing on a per-device basis
> tpm_tis: Do not fall back to a hardcoded address for TPM2
> tpm_tis: Use devm_ioremap_resource
> tpm_tis: Clean up the force=1 module parameter
> tpm_crb: Drop le32_to_cpu(ioread32(..))
> tpm_crb: Use devm_ioremap_resource
>
> Jerry Snitselaar (1):
> tpm: remove unneeded include of actbl2.h
>
> drivers/char/tpm/tpm.h | 7 --
> drivers/char/tpm/tpm2-cmd.c | 12 +--
> drivers/char/tpm/tpm_crb.c | 194 ++++++++++++++++++++-------------
> drivers/char/tpm/tpm_tis.c | 255 +++++++++++++++++++++++++-------------------
> include/keys/trusted-type.h | 2 +-
> security/keys/trusted.c | 11 +-
> 6 files changed, 272 insertions(+), 209 deletions(-)
> --
> To unsubscribe from this list: send the line "unsubscribe keyrings" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-02-08 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 23:39 [GIT PULL] tpmdd fixes for Linux 4.5 Jarkko Sakkinen
2016-02-08 20:46 ` Jarkko Sakkinen [this message]
2016-02-09 0:59 ` James Morris
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=20160208204610.GA14626@intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--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