From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, gregkh@linuxfoundation.org,
Ulf Hansson <ulf.hansson@linaro.org>,
Adrian Hunter <adrian.hunter@intel.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Vinayak Holikatti <vinholikatti@gmail.com>,
Christoph Hellwig <hch@lst.de>,
Yaniv Gardi <ygardi@codeaurora.org>,
Joao Pinto <Joao.Pinto@synopsys.com>,
linux-mmc@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org,
Tomas Winkler <tomas.winkler@intel.com>
Subject: Re: [PATCH 4/8] char: rpmb: provide user space interface
Date: Sun, 3 Apr 2016 18:36:08 +0800 [thread overview]
Message-ID: <201604031822.7UBwspdK%fengguang.wu@intel.com> (raw)
In-Reply-To: <1459676572-29921-5-git-send-email-tomas.winkler@intel.com>
Hi Tomas,
[auto build test WARNING on char-misc/char-misc-testing]
[also build test WARNING on v4.6-rc1 next-20160401]
[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/Tomas-Winkler/Replay-Protected-Memory-Block-RPMB-subsystem/20160403-174929
coccinelle warnings: (new ones prefixed by >>)
>> drivers/char/rpmb/cdev.c:94:13-20: WARNING opportunity for memdup_user
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-04-03 10:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-03 9:42 [PATCH 0/8] Replay Protected Memory Block (RPMB) subsystem Tomas Winkler
2016-04-03 9:42 ` [PATCH 1/8] rpmb: add " Tomas Winkler
2016-04-03 9:42 ` [PATCH 2/8] char: rpmb: add sysfs-class ABI documentation Tomas Winkler
2016-04-24 9:19 ` Pavel Machek
2016-04-24 16:27 ` Winkler, Tomas
2016-04-03 9:42 ` [PATCH 3/8] char: rpmb: add device attributes Tomas Winkler
2016-04-03 9:42 ` [PATCH 4/8] char: rpmb: provide user space interface Tomas Winkler
2016-04-03 10:36 ` kbuild test robot [this message]
2016-04-03 10:36 ` [PATCH] char: rpmb: fix memdup_user.cocci warnings kbuild test robot
2016-04-03 9:42 ` [PATCH 5/8] char: rpmb: add RPMB simulation device Tomas Winkler
2016-04-03 10:45 ` kbuild test robot
2016-04-03 10:45 ` [PATCH] char: rpmb: fix platform_no_drv_owner.cocci warnings kbuild test robot
2016-04-03 15:35 ` [PATCH 5/8] char: rpmb: add RPMB simulation device kbuild test robot
2016-04-03 9:42 ` [PATCH 6/8] tools rpmb: add RPBM access tool Tomas Winkler
2016-04-04 0:55 ` kbuild test robot
2016-04-03 9:42 ` [PATCH 7/8] mmc: block: register rpmb partition with the RPMB subsystem Tomas Winkler
2016-04-03 9:42 ` [PATCH 8/8] scsi: ufs: connect to " Tomas Winkler
2016-04-04 10:32 ` Joao Pinto
2016-04-04 10:35 ` Winkler, Tomas
2016-04-03 13:27 ` [PATCH 0/8] Replay Protected Memory Block (RPMB) subsystem Andy Lutomirski
2016-04-03 19:27 ` Winkler, Tomas
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=201604031822.7UBwspdK%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Joao.Pinto@synopsys.com \
--cc=adrian.hunter@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=tomas.winkler@intel.com \
--cc=ulf.hansson@linaro.org \
--cc=vinholikatti@gmail.com \
--cc=ygardi@codeaurora.org \
/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).