From: <Peter.Huewe@infineon.com>
To: <key@linux.vnet.ibm.com>
Cc: <jmorris@namei.org>, <linux-kernel@vger.kernel.org>,
<linux-security-module@vger.kernel.org>,
<tpmdd-devel@lists.sourceforge.net>, <bfreed@chromium.org>,
<safford@linux.vnet.ibm.com>, <hpa@linux.intel.com>
Subject: RE: [PATCH] char/tpm: Use struct dev_pm_ops for power management.
Date: Tue, 7 Aug 2012 07:30:35 +0000 [thread overview]
Message-ID: <74A44E99E3274B4CB570415926B37D440E0CC7@MUCSE501.eu.infineon.com> (raw)
In-Reply-To: <20120806192957.GB6821@linux.vnet.ibm.com>
Hi Kent,
> Thanks Peter. One more request - can you roll this fix into the driver
> patch itself and just add a note in the change log? Sorry I didn't
> mention this before.
Yes I'll do that.
And while at it I'll also replace our i2c_transfer_nolock with the new (in 3.6rc-1) __i2c_transfer function and
integrate Bryans Patch directly into the driver.
Peter
next prev parent reply other threads:[~2012-08-07 7:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120730210522.GA23790@linux.vnet.ibm.com>
2012-08-03 4:40 ` New TPM driver, hwrng driver and fixes (2) James Morris
2012-08-03 4:45 ` James Morris
2012-08-03 7:42 ` Peter.Huewe
2012-08-03 14:51 ` [PATCH] char/tpm: Fix compile error if CONFIG_PM is not set in tpm_i2c_infineon Peter Huewe
2012-08-03 20:38 ` Kent Yoder
2012-08-06 7:58 ` [PATCH] char/tpm: Use struct dev_pm_ops for power management Peter Huewe
2012-08-06 19:29 ` Kent Yoder
2012-08-07 7:30 ` Peter.Huewe [this message]
2012-08-07 9:42 ` [PATCH] char/tpm: Add new driver for Infineon I2C TIS TPM Peter Huewe
2012-12-05 23:09 [tpmdd-devel] [PATCH 1/1] TPM: STMicroelectronics ST33 I2C KERNEL 3.x.x Kent Yoder
2012-12-06 0:20 ` [PATCH] char/tpm: Use struct dev_pm_ops for power management Peter Huewe
2012-12-06 15:07 ` Kent Yoder
2012-12-10 18:11 ` Mathias LEBLANC
2012-12-06 16:27 ` Kent Yoder
2012-12-08 3:55 ` Peter Hüwe
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=74A44E99E3274B4CB570415926B37D440E0CC7@MUCSE501.eu.infineon.com \
--to=peter.huewe@infineon.com \
--cc=bfreed@chromium.org \
--cc=hpa@linux.intel.com \
--cc=jmorris@namei.org \
--cc=key@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=safford@linux.vnet.ibm.com \
--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 NNTP newsgroup(s).