From: jarkko.sakkinen@linux.intel.com (Jarkko Sakkinen)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] tpm/tpm_crb: Access locality for non-ACPI and non-SMC start method
Date: Fri, 25 Aug 2017 20:35:02 +0300 [thread overview]
Message-ID: <20170825173502.q5oc3uovpvzi65dm@linux.intel.com> (raw)
In-Reply-To: <b1179dde-46af-7172-3f84-e8cabffa05d5@codeaurora.org>
On Fri, Aug 25, 2017 at 12:28:21PM -0500, Jiandi An wrote:
>
>
> 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.
Great
/Jarkko
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-08-25 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1503029736-591-1-git-send-email-anjiandi@codeaurora.org>
[not found] ` <20170822173956.zpqe4scdnv7plrhj@linux.intel.com>
[not found] ` <d88e255c-f8c9-b6fc-64bd-8cf56153fcce@codeaurora.org>
[not found] ` <20170824122630.75sxjmkj5f7p7tv5@linux.intel.com>
[not found] ` <7478e964-6553-9d1e-3d8f-83b044a9a562@codeaurora.org>
2017-08-25 16:21 ` [PATCH] tpm/tpm_crb: Access locality for non-ACPI and non-SMC start method Jarkko Sakkinen
2017-08-25 16:53 ` Jason Gunthorpe
2017-08-25 17:28 ` Jiandi An
2017-08-25 17:35 ` 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=20170825173502.q5oc3uovpvzi65dm@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=linux-security-module@vger.kernel.org \
/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).