From: Jarkko Sakkinen <jarkko.sakkinen@intel.com>
To: "Peter Hüwe" <PeterHuewe@gmx.de>
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
"moderated list:TPM DEVICE DRIVER"
<tpmdd-devel@lists.sourceforge.net>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [tpmdd-devel] [PATCH] tpm, tpm_crb: migrate to struct acpi_table_tpm2 and acpi_tpm2_control
Date: Mon, 22 Jun 2015 16:04:00 +0300 [thread overview]
Message-ID: <20150622130400.GB6048@intel.com> (raw)
In-Reply-To: <201506162246.51398.PeterHuewe@gmx.de>
On Tue, Jun 16, 2015 at 10:46:50PM +0200, Peter Hüwe wrote:
> Hi Jarkko
>
> > > > >Betreff: [PATCH] tpm, tpm_crb: migrate to struct acpi_table_tpm2 and
> > > > >acpi_tpm2_control
> > > > but are the names there still correct? Isn't this information outdated?
> > > > The acpi spec refers to the MS spec which is not present anymore, and
> > > > MS refers to the TCG -- and in the PTP your names are used.
> > > >
> > > > ---> We should update the ACPI header?
> > > > At least the naming for reserved and error.
> > > > What do you think?
> > >
> > > I think you are right. It does not make sense to degrade here.
>
> so I'm waiting on the new version depending on the updated acpi header?
Yes. I'll submit a new patch later on when new arrives come from ACPICA.
You can ignore this until then.
> Thanks,
> Peter
/Jarkko
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2015-06-22 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 15:57 [PATCH] tpm, tpm_crb: migrate to struct acpi_table_tpm2 and acpi_tpm2_control Jarkko Sakkinen
2015-06-02 14:00 ` Aw: " Peter Huewe
2015-06-08 11:54 ` Jarkko Sakkinen
2015-06-09 9:14 ` [tpmdd-devel] " Jarkko Sakkinen
2015-06-16 20:46 ` Peter Hüwe
2015-06-22 13:04 ` Jarkko Sakkinen [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=20150622130400.GB6048@intel.com \
--to=jarkko.sakkinen@intel.com \
--cc=PeterHuewe@gmx.de \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-kernel@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