From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Sasha Levin <Alexander.Levin@microsoft.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Tomas Winkler <tomas.winkler@intel.com>
Subject: Re: [PATCH] tpm: separate cmd_ready/go_idle from runtime_pm
Date: Tue, 18 Sep 2018 00:14:10 +0300 [thread overview]
Message-ID: <20180917211410.GB6716@linux.intel.com> (raw)
In-Reply-To: <20180917044706.GA19145@kroah.com>
On Mon, Sep 17, 2018 at 06:47:06AM +0200, Greg KH wrote:
> On Mon, Sep 17, 2018 at 12:55:24AM +0000, Sasha Levin wrote:
> > On Sun, Sep 16, 2018 at 02:46:42PM +0200, Greg KH wrote:
> > >On Sun, Sep 16, 2018 at 03:02:27PM +0300, Jarkko Sakkinen wrote:
> > >> From: Tomas Winkler <tomas.winkler@intel.com>
> > >>
> > >> commit 627448e85c766587f6fdde1ea3886d6615081c77 upstream
> > >
> > >Are you sure? That commit is not in Linus's tree :(
> >
> > Are you sure? I see it went in during the 4.19 merge window.
>
> Ugh, it's been a long week, sorry, you are right, my mistake, I was in
> the wrong git repo when I checked this.
>
> greg k-h
Anyway remainded me that one should is always double check the mainline
tree (which I admit did not do, only James Morris' tree).
/Jarkko
next prev parent reply other threads:[~2018-09-18 2:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-16 12:02 [PATCH] tpm: separate cmd_ready/go_idle from runtime_pm Jarkko Sakkinen
2018-09-16 12:46 ` Greg KH
2018-09-17 0:55 ` Sasha Levin
2018-09-17 4:47 ` Greg KH
2018-09-17 21:14 ` Jarkko Sakkinen [this message]
2018-09-17 7:21 ` Winkler, Tomas
2018-09-17 9:30 ` Greg KH
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=20180917211410.GB6716@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=Alexander.Levin@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).