From: Jarkko Sakkinen <jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: James Morris <jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org>
Cc: tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
keyrings-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [GIT PULL] tpmdd fix
Date: Fri, 26 Feb 2016 11:36:43 +0200 [thread overview]
Message-ID: <20160226093643.GA16778@intel.com> (raw)
Hi James,
this is the fix for the build warning.
/Jarkko
The following changes since commit 481873d06f2bf2ad732450a3a5fa5b8c2a07ef88:
Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity into next (2016-02-26 15:06:41 +1100)
are available in the git repository at:
https://github.com/jsakkine/linux-tpmdd.git tags/tpmdd-next-20160226
for you to fetch changes up to 2cb6d6460f1a171c71c134e0efe3a94c2206d080:
tpm_tis: fix build warning with tpm_tis_resume (2016-02-26 11:32:07 +0200)
----------------------------------------------------------------
tpmdd fix
----------------------------------------------------------------
Jarkko Sakkinen (1):
tpm_tis: fix build warning with tpm_tis_resume
drivers/char/tpm/tpm_tis.c | 2 ++
1 file changed, 2 insertions(+)
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
WARNING: multiple messages have this Message-ID (diff)
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: [GIT PULL] tpmdd fix
Date: Fri, 26 Feb 2016 11:36:43 +0200 [thread overview]
Message-ID: <20160226093643.GA16778@intel.com> (raw)
Hi James,
this is the fix for the build warning.
/Jarkko
The following changes since commit 481873d06f2bf2ad732450a3a5fa5b8c2a07ef88:
Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity into next (2016-02-26 15:06:41 +1100)
are available in the git repository at:
https://github.com/jsakkine/linux-tpmdd.git tags/tpmdd-next-20160226
for you to fetch changes up to 2cb6d6460f1a171c71c134e0efe3a94c2206d080:
tpm_tis: fix build warning with tpm_tis_resume (2016-02-26 11:32:07 +0200)
----------------------------------------------------------------
tpmdd fix
----------------------------------------------------------------
Jarkko Sakkinen (1):
tpm_tis: fix build warning with tpm_tis_resume
drivers/char/tpm/tpm_tis.c | 2 ++
1 file changed, 2 insertions(+)
next reply other threads:[~2016-02-26 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 9:36 Jarkko Sakkinen [this message]
2016-02-26 9:36 ` [GIT PULL] tpmdd fix Jarkko Sakkinen
2016-02-29 7:28 ` 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=20160226093643.GA16778@intel.com \
--to=jarkko.sakkinen-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org \
--cc=keyrings-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 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.