From: Jiandi An <anjiandi@codeaurora.org>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: peterhuewe@gmx.de, tpmdd@selhorst.net,
tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] tpm/tpm_crb: Access locality for non-ACPI and non-SMC start method
Date: Fri, 25 Aug 2017 12:28:21 -0500 [thread overview]
Message-ID: <b1179dde-46af-7172-3f84-e8cabffa05d5@codeaurora.org> (raw)
In-Reply-To: <20170825165309.GB5254@obsidianresearch.com>
On 08/25/2017 11:53 AM, Jason Gunthorpe wrote:
> On Fri, Aug 25, 2017 at 07:21:39PM +0300, Jarkko Sakkinen wrote:
>> As I said before it would make much more sense to make code always deal
>> with sm and remove flags completely. That would help maintaining code
>> easier as new logic for TZ is introduced.
>
> Yes please
>
> Jason
>
Okay, I'll work on moving sm to priv and getting rid of flags from
priv. Will submit a new patch with appropriate patch name and not
a v2 of this patch since the scope of changes have changed.
Thanks for your comments and feedback.
--
Jiandi An
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm
Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a
Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-08-25 17:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 4:15 [PATCH] tpm/tpm_crb: Access locality for non-ACPI and non-SMC start method Jiandi An
2017-08-19 17:05 ` Jarkko Sakkinen
2017-08-21 3:41 ` Jiandi An
2017-08-22 17:36 ` Jarkko Sakkinen
2017-08-22 17:39 ` Jarkko Sakkinen
2017-08-22 21:28 ` Jiandi An
[not found] ` <d88e255c-f8c9-b6fc-64bd-8cf56153fcce-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-08-23 2:25 ` Jason Gunthorpe
2017-08-24 12:26 ` Jarkko Sakkinen
2017-08-24 17:20 ` Jiandi An
2017-08-25 16:21 ` Jarkko Sakkinen
2017-08-25 16:53 ` Jason Gunthorpe
2017-08-25 17:28 ` Jiandi An [this message]
2017-08-25 17:35 ` Jarkko Sakkinen
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=b1179dde-46af-7172-3f84-e8cabffa05d5@codeaurora.org \
--to=anjiandi@codeaurora.org \
--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: 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).