From: Nayna <nayna@linux.vnet.ibm.com> To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> Cc: tpmdd-devel@lists.sourceforge.net, peterhuewe@gmx.de, tpmdd@selhorst.net, jgunthorpe@obsidianresearch.com, linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org Subject: Re: [PATCH v6 0/9] tpm: cleanup/fixes in existing event log support Date: Tue, 15 Nov 2016 11:05:42 +0530 [thread overview] Message-ID: <582A9EAE.5000505@linux.vnet.ibm.com> (raw) In-Reply-To: <20161115021543.d4wgjqid7fut4y4c@intel.com> On 11/15/2016 07:45 AM, Jarkko Sakkinen wrote: > On Mon, Nov 14, 2016 at 04:25:14PM -0800, Jarkko Sakkinen wrote: >> On Mon, Nov 14, 2016 at 02:33:23PM -0800, Jarkko Sakkinen wrote: >>> On Mon, Nov 14, 2016 at 05:00:47AM -0500, Nayna Jain wrote: >>>> This patch set includes the cleanup and bug fixes patches, previously >>>> part of the "tpm: add the securityfs pseudo files support for TPM 2.0 >>>> firmware event log" patch set, in order to upstream them more quickly. >>> >>> I applied the patches. I'm not yet sure whether these are part of the >>> 4.10 pull request or whether I postpone to 4.11 (my preference would be >>> 4.10 but I do not want to close that right now). I'll do testing next >>> week before doing pull request. >>> >>> I hope that the commits gets some reviews and testing now that they are >>> easily testable in my master branch. >> >> Event log still works and they do not seem to break TPM 2.0 (tried both >> machine with tpm_crb and tpm_tis). >> >> Stefan: would you mind check that these do not break your TPM 1.2 >> environment? I already tried wih TPM 1.2 machine but probably would >> make sense to peer test. > > I'm dropping commits 8/9 and 9/9 from my tree and *will not* include > them to my 4.10 pull request. Will fix this and resend the patch 8/9 and 9/9 again. Thanks & Regards, - Nayna > > /Jarkko >
WARNING: multiple messages have this Message-ID (diff)
From: Nayna <nayna-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org> To: Jarkko Sakkinen <jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org> Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Subject: Re: [PATCH v6 0/9] tpm: cleanup/fixes in existing event log support Date: Tue, 15 Nov 2016 11:05:42 +0530 [thread overview] Message-ID: <582A9EAE.5000505@linux.vnet.ibm.com> (raw) In-Reply-To: <20161115021543.d4wgjqid7fut4y4c-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> On 11/15/2016 07:45 AM, Jarkko Sakkinen wrote: > On Mon, Nov 14, 2016 at 04:25:14PM -0800, Jarkko Sakkinen wrote: >> On Mon, Nov 14, 2016 at 02:33:23PM -0800, Jarkko Sakkinen wrote: >>> On Mon, Nov 14, 2016 at 05:00:47AM -0500, Nayna Jain wrote: >>>> This patch set includes the cleanup and bug fixes patches, previously >>>> part of the "tpm: add the securityfs pseudo files support for TPM 2.0 >>>> firmware event log" patch set, in order to upstream them more quickly. >>> >>> I applied the patches. I'm not yet sure whether these are part of the >>> 4.10 pull request or whether I postpone to 4.11 (my preference would be >>> 4.10 but I do not want to close that right now). I'll do testing next >>> week before doing pull request. >>> >>> I hope that the commits gets some reviews and testing now that they are >>> easily testable in my master branch. >> >> Event log still works and they do not seem to break TPM 2.0 (tried both >> machine with tpm_crb and tpm_tis). >> >> Stefan: would you mind check that these do not break your TPM 1.2 >> environment? I already tried wih TPM 1.2 machine but probably would >> make sense to peer test. > > I'm dropping commits 8/9 and 9/9 from my tree and *will not* include > them to my 4.10 pull request. Will fix this and resend the patch 8/9 and 9/9 again. Thanks & Regards, - Nayna > > /Jarkko > ------------------------------------------------------------------------------
next prev parent reply other threads:[~2016-11-15 5:36 UTC|newest] Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-11-14 10:00 [PATCH v6 0/9] tpm: cleanup/fixes in existing event log support Nayna Jain 2016-11-14 10:00 ` [PATCH v6 1/9] tpm: define a generic open() method for ascii & bios measurements Nayna Jain 2016-11-14 10:00 ` Nayna Jain 2016-11-14 10:00 ` [PATCH v6 2/9] tpm: replace symbolic permission with octal for securityfs files Nayna Jain 2016-11-14 22:18 ` Jarkko Sakkinen 2016-11-14 22:18 ` Jarkko Sakkinen 2016-11-14 22:21 ` Jarkko Sakkinen 2016-11-14 22:21 ` Jarkko Sakkinen 2016-11-15 0:11 ` [tpmdd-devel] " Jarkko Sakkinen 2016-11-15 0:11 ` Jarkko Sakkinen 2016-11-14 10:00 ` [PATCH v6 3/9] tpm: replace dynamically allocated bios_dir with a static array Nayna Jain 2016-11-14 10:00 ` Nayna Jain 2016-11-22 11:23 ` Jarkko Sakkinen 2016-11-22 16:58 ` Jason Gunthorpe 2016-11-22 16:58 ` Jason Gunthorpe 2016-11-24 13:57 ` Jarkko Sakkinen 2016-11-24 13:57 ` Jarkko Sakkinen 2016-11-24 16:53 ` Jason Gunthorpe 2016-11-24 16:53 ` Jason Gunthorpe 2016-11-25 8:08 ` Jarkko Sakkinen 2016-11-25 8:08 ` Jarkko Sakkinen 2016-11-25 19:38 ` Jason Gunthorpe 2016-11-26 12:54 ` Jarkko Sakkinen 2016-11-22 19:26 ` Nayna 2016-11-24 14:01 ` Jarkko Sakkinen 2016-11-14 10:00 ` [PATCH v6 4/9] tpm: drop tpm1_chip_register(/unregister) Nayna Jain 2016-11-14 10:00 ` Nayna Jain 2016-11-22 11:22 ` Jarkko Sakkinen 2016-11-22 16:42 ` Jason Gunthorpe 2016-11-22 16:42 ` Jason Gunthorpe 2016-11-23 18:33 ` Nayna 2016-11-23 18:33 ` Nayna 2016-11-24 11:52 ` Jarkko Sakkinen 2016-11-24 11:51 ` Jarkko Sakkinen 2016-11-24 11:51 ` Jarkko Sakkinen 2016-11-14 10:00 ` [PATCH v6 5/9] tpm: have event log use the tpm_chip Nayna Jain 2016-11-14 10:00 ` Nayna Jain 2016-11-14 23:44 ` Jarkko Sakkinen 2016-11-15 0:12 ` Jarkko Sakkinen 2016-11-15 0:12 ` Jarkko Sakkinen 2016-11-14 10:00 ` [PATCH v6 6/9] tpm: fix the missing .owner in tpm_bios_measurements_ops Nayna Jain 2016-11-14 10:00 ` Nayna Jain 2016-11-14 22:22 ` Jarkko Sakkinen 2016-11-15 0:13 ` Jarkko Sakkinen 2016-11-14 10:00 ` [PATCH v6 7/9] tpm: redefine read_log() to handle ACPI/OF at runtime Nayna Jain 2016-11-14 10:00 ` Nayna Jain 2016-11-15 0:14 ` Jarkko Sakkinen 2016-11-14 10:00 ` [PATCH v6 8/9] tpm: replace of_find_node_by_name() with dev of_node property Nayna Jain 2016-11-14 10:00 ` Nayna Jain 2016-11-14 10:00 ` [PATCH v6 9/9] tpm: cleanup of printk error messages Nayna Jain 2016-11-14 10:00 ` Nayna Jain 2016-11-14 22:24 ` Jarkko Sakkinen 2016-11-14 22:24 ` Jarkko Sakkinen 2016-11-15 0:15 ` Jarkko Sakkinen 2016-11-14 22:33 ` [PATCH v6 0/9] tpm: cleanup/fixes in existing event log support Jarkko Sakkinen 2016-11-14 22:33 ` Jarkko Sakkinen 2016-11-15 0:25 ` Jarkko Sakkinen 2016-11-15 0:30 ` Jarkko Sakkinen 2016-11-15 0:30 ` Jarkko Sakkinen 2016-11-15 2:15 ` Jarkko Sakkinen 2016-11-15 5:35 ` Nayna [this message] 2016-11-15 5:35 ` Nayna 2016-11-15 17:40 ` Jarkko Sakkinen 2016-11-15 18:06 ` Jason Gunthorpe 2016-11-15 18:54 ` Jarkko Sakkinen 2016-11-19 18:36 ` Jason Gunthorpe 2016-11-19 18:36 ` Jason Gunthorpe 2016-11-20 9:58 ` Jarkko Sakkinen 2016-11-21 18:25 ` Jason Gunthorpe
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=582A9EAE.5000505@linux.vnet.ibm.com \ --to=nayna@linux.vnet.ibm.com \ --cc=jarkko.sakkinen@linux.intel.com \ --cc=jgunthorpe@obsidianresearch.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-security-module@vger.kernel.org \ --cc=peterhuewe@gmx.de \ --cc=tpmdd-devel@lists.sourceforge.net \ --cc=tpmdd@selhorst.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: linkBe 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.