From: Tadeusz Struk <tadeusz.struk@intel.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, jarkko.sakkinen@linux.intel.com, jgg@ziepe.ca,
linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] tpm: add support for nonblocking operation
Date: Mon, 11 Jun 2018 21:46:35 -0700 [thread overview]
Message-ID: <359fe9af-ba17-e23b-a21e-c3c94f23b5ff@intel.com> (raw)
In-Reply-To: <201806120803.W0vjfLEH%fengguang.wu@intel.com>
On 06/11/2018 07:53 PM, kbuild test robot wrote:
> Hi Tadeusz,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on char-misc/char-misc-testing]
> [also build test ERROR on next-20180608]
> [cannot apply to v4.17]
Hi,
Thanks for the report. This patch should go on top of
https://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git/?h=next-tpm
I will check the config tomorrow.
Thanks,
--
Tadeusz
next prev parent reply other threads:[~2018-06-12 4:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 23:29 [PATCH] tpm: add support for nonblocking operation Tadeusz Struk
2018-06-01 14:37 ` Jason Gunthorpe
2018-06-01 16:55 ` Tadeusz Struk
2018-06-01 17:17 ` Jason Gunthorpe
2018-06-12 0:20 ` [PATCH v2 0/2] " Tadeusz Struk
2018-06-12 0:20 ` [PATCH v2 1/2] tpm: add ptr to the tpm_space struct to file_priv Tadeusz Struk
2018-06-12 0:20 ` [PATCH v2 2/2] tpm: add support for nonblocking operation Tadeusz Struk
2018-06-12 2:53 ` kbuild test robot
2018-06-12 4:46 ` Tadeusz Struk [this message]
2018-06-12 17:39 ` Tadeusz Struk
2018-06-04 19:55 ` [PATCH] " Jarkko Sakkinen
2018-06-04 19:56 ` Jarkko Sakkinen
2018-06-08 19:36 ` flihp
2018-06-12 0:13 ` Tadeusz Struk
2018-06-18 18:26 ` Jarkko Sakkinen
2018-06-12 1:43 ` James Bottomley
2018-06-18 18:25 ` Jarkko Sakkinen
2018-07-05 23:15 ` flihp
2018-07-16 17:34 ` Jarkko Sakkinen
2018-07-16 20:10 ` Tadeusz Struk
2018-07-23 17:38 ` 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=359fe9af-ba17-e23b-a21e-c3c94f23b5ff@intel.com \
--to=tadeusz.struk@intel.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=kbuild-all@01.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lkp@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