From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: "Winkler, Tomas" <tomas.winkler@intel.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Alan Cox <alan@linux.intel.com>,
"Shevchenko, Andriy" <andriy.shevchenko@intel.com>,
"Struk, Tadeusz" <tadeusz.struk@intel.com>
Cc: "Usyskin, Alexander" <alexander.usyskin@intel.com>,
"linux-integrity@vger.kernel.org"
<linux-integrity@vger.kernel.org>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v7] tpm: separate cmd_ready/go_idle from runtime_pm
Date: Thu, 28 Jun 2018 16:30:49 +0300 [thread overview]
Message-ID: <722fe86b2651d2616fa9bf43d9f8b1322f4c868b.camel@linux.intel.com> (raw)
In-Reply-To: <5B8DA87D05A7694D9FA63FD143655C1B9D956753@hasmsx108.ger.corp.intel.com>
On Wed, 2018-06-27 at 21:13 +0000, Winkler, Tomas wrote:
> Very well, I will remove the NESTED flag. though I have feeling you are
> shooting from the hip you didn't really read the code.
> Please there anyone who can review the code?
Asking to change a minor thing in a patch does not really fit into that
profile. I've even tried the patch a few times in it seems to work just
fine. You are making a big deal out of nothing.
/Jarkko
next prev parent reply other threads:[~2018-06-28 13:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-24 20:52 [PATCH v7] tpm: separate cmd_ready/go_idle from runtime_pm Tomas Winkler
2018-06-25 16:24 ` Jarkko Sakkinen
2018-06-25 16:30 ` Jarkko Sakkinen
2018-06-26 21:15 ` Winkler, Tomas
2018-06-27 16:42 ` Jarkko Sakkinen
2018-06-27 21:13 ` Winkler, Tomas
2018-06-28 13:30 ` Jarkko Sakkinen [this message]
2018-06-28 15:02 ` Winkler, Tomas
2018-06-25 18:50 ` Winkler, Tomas
2018-06-26 8:22 ` 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=722fe86b2651d2616fa9bf43d9f8b1322f4c868b.camel@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=alan@linux.intel.com \
--cc=alexander.usyskin@intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tadeusz.struk@intel.com \
--cc=tomas.winkler@intel.com \
/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