From: kbuild test robot <lkp@intel.com>
To: Tadeusz Struk <tadeusz.struk@intel.com>
Cc: kbuild-all@01.org, jarkko.sakkinen@linux.intel.com, jgg@ziepe.ca,
linux-integrity@vger.kernel.org, tadeusz.struk@intel.com,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] tpm: add support for nonblocking operation
Date: Tue, 12 Jun 2018 10:53:25 +0800 [thread overview]
Message-ID: <201806120803.W0vjfLEH%fengguang.wu@intel.com> (raw)
In-Reply-To: <152876282414.19591.7972634639749417028.stgit@tstruk-mobl1.jf.intel.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: multipart/mixed; boundary="OXfL5xGRrasGEqWY", Size: 1628 bytes --]
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]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Tadeusz-Struk/tpm-add-ptr-to-the-tpm_space-struct-to-file_priv/20180612-082203
config: i386-randconfig-x008-201823 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All error/warnings (new ones prefixed by >>):
>> drivers/char//tpm/tpm-dev-common.c:223:1: warning: data definition has no type or storage class
__exitcall(tpm_dev_common_exit);
^~~~~~~~~~
>> drivers/char//tpm/tpm-dev-common.c:223:1: error: type defaults to 'int' in declaration of '__exitcall' [-Werror=implicit-int]
>> drivers/char//tpm/tpm-dev-common.c:223:1: warning: parameter names (without types) in function declaration
drivers/char//tpm/tpm-dev-common.c:215:20: warning: 'tpm_dev_common_exit' defined but not used [-Wunused-function]
static void __exit tpm_dev_common_exit(void)
^~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +223 drivers/char//tpm/tpm-dev-common.c
222
> 223 __exitcall(tpm_dev_common_exit);
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[ Part 2, Application/GZIP 28 KB. ]
[ Unable to print this part. ]
next prev parent reply other threads:[~2018-06-12 2:53 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 [this message]
2018-06-12 4:46 ` Tadeusz Struk
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=201806120803.W0vjfLEH%fengguang.wu@intel.com \
--to=lkp@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=tadeusz.struk@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