From: kbuild test robot <lkp@intel.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: kbuild-all@01.org,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
Peter Huewe <peterhuewe@gmx.de>
Subject: Re: [PATCH v4 7/7] tpm_crb: Use devm_ioremap_resource
Date: Fri, 8 Jan 2016 10:04:40 +0800 [thread overview]
Message-ID: <201601081058.vDvDPN9c%fengguang.wu@intel.com> (raw)
In-Reply-To: <1452213386-21460-8-git-send-email-jgunthorpe@obsidianresearch.com>
Hi Jason,
[auto build test WARNING on next-20160107]
[cannot apply to char-misc/char-misc-testing v4.4-rc8 v4.4-rc7 v4.4-rc6 v4.4-rc8]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Jason-Gunthorpe/tpm_tis-Clean-up-force-module-parameter/20160108-084227
coccinelle warnings: (new ones prefixed by >>)
>> drivers/char/tpm/tpm_crb.c:297:1-3: WARNING: PTR_ERR_OR_ZERO can be used
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2016-01-08 2:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 0:36 [PATCH v4 0/7] tpm_tis: Clean up force module parameter Jason Gunthorpe
2016-01-08 0:36 ` [PATCH v4 1/7] tpm_crb: Use the common ACPI definition of struct acpi_tpm2 Jason Gunthorpe
2016-01-08 12:01 ` Jarkko Sakkinen
2016-01-08 0:36 ` [PATCH v4 2/7] tpm_tis: Disable interrupt auto probing on a per-device basis Jason Gunthorpe
2016-01-08 0:36 ` [PATCH v4 3/7] tpm_tis: Do not fall back to a hardcoded address for TPM2 Jason Gunthorpe
2016-01-08 12:01 ` Jarkko Sakkinen
2016-01-08 0:36 ` [PATCH v4 4/7] tpm_tis: Use devm_ioremap_resource Jason Gunthorpe
2016-01-08 0:36 ` [PATCH v4 5/7] tpm_tis: Clean up the force=1 module parameter Jason Gunthorpe
2016-01-08 12:01 ` Jarkko Sakkinen
2016-01-08 0:36 ` [PATCH v4 6/7] tpm_crb: Drop le32_to_cpu(ioread32(..)) Jason Gunthorpe
2016-01-08 0:36 ` [PATCH v4 7/7] tpm_crb: Use devm_ioremap_resource Jason Gunthorpe
2016-01-08 2:04 ` kbuild test robot [this message]
2016-01-08 2:04 ` [PATCH] tpm_crb: fix ptr_ret.cocci warnings kbuild test robot
2016-01-08 12:00 ` [PATCH v4 7/7] tpm_crb: Use devm_ioremap_resource Jarkko Sakkinen
2016-01-08 12:02 ` Jarkko Sakkinen
2016-01-08 15:12 ` [PATCH v4 0/7] tpm_tis: Clean up force module parameter 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=201601081058.vDvDPN9c%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=tpmdd-devel@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®