Re: [PATCH v9 0/3] Enable PPI sysfs interface for TPM 2.0
From: Jarkko Sakkinen
Date: Wed Aug 26 2015 - 01:28:31 EST
On Tue, Aug 25, 2015 at 07:20:24PM +0200, Peter Huewe wrote:
> Will look at it as soon as possible - relocating to the us is quite stressful.sorry about that.
> But since we are already at v9 i think it is in a good shape.
Alright, thanks for informing about this!
> Am 25. August 2015 19:03:27 MESZ, schrieb Jarkko Sakkinen <jarkko.sakkinen@xxxxxxxxx>:
> >Does this start be in the shape that there would be chance to pull this
> >in at some point? To be able to enable TPM 2.0 chips from Linux is
> >mandatory feature in my opinion.
> >Thank you.
> >On Wed, Aug 12, 2015 at 05:05:40PM +0300, Jarkko Sakkinen wrote:
> >> v9:
> >> * Fixed naming for __compat_only_sysfs_link_entry_to_kobj()
> >> v8:
> >> * Renamed sysfs_link_entry_to_kobj() to
> >> __compat_only_sysfs_link_entry_to_kobj()
> >> v7:
> >> * Fixed compile error when CONFIG_SYSFS is not enabled.
> >> v6:
> >> * Updated documentation.
> >> v5:
> >> * Removed dangling export of kernfs_remove_by_name_ns() from the
> >> patch.
> >> v4:
> >> * Use sysfs_remove_link()
> >> v3:
> >> * Fixed to_tpm_chip() macro.
> >> * Split into two patches.
> >> * Renamed sysfs_link_group_to_kobj to sysfs_link_entry_to_kobj
> >> * Only create the "backwards compatibility" symlink for TPM 1.x
> >> Jarkko Sakkinen (3):
> >> sysfs: added __compat_only_sysfs_link_entry_to_kobj()
> >> tpm: move the PPI attributes to character device directory.
> >> tpm: update PPI documentation to address the location change.
> >> Documentation/ABI/testing/sysfs-driver-ppi | 19 ++++++++-----
> >> drivers/char/tpm/tpm-chip.c | 24 ++++++++++------
> >> drivers/char/tpm/tpm.h | 17 ++++--------
> >> drivers/char/tpm/tpm_ppi.c | 34
> >> fs/sysfs/group.c | 44
> >> include/linux/sysfs.h | 11 ++++++++
> >> 6 files changed, 100 insertions(+), 49 deletions(-)
> >> --
> >> 2.5.0
> Sent from my mobile
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/