From: kbuild test robot <lkp@intel.com>
To: Chen Feng <puck.chen@hisilicon.com>
Cc: kbuild-all@01.org, lee.jones@linaro.org,
linux-kernel@vger.kernel.org, lgirdwood@gmail.com,
broonie@kernel.org, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, xuwei5@hisilicon.com,
puck.chen@hisilicon.com, puck.chen@aliyun.com,
yudongbin@hisilicon.com, saberlily.xia@hisilicon.com,
suzhuangluan@hisilicon.com, kong.kongxinwei@hisilicon.com,
xuyiping@hisilicon.com, z.liuxinliang@hisilicon.com,
weidong2@hisilicon.com, w.f@huawei.com, qijiwen@hisilicon.com,
peter.panshilin@hisilicon.com, dan.zhao@hisilicon.com,
linuxarm@huawei.com
Subject: Re: [PATCH v3 3/5] mfd: hi655x: Add hi665x pmic driver
Date: Tue, 15 Dec 2015 21:29:18 +0800 [thread overview]
Message-ID: <201512152147.S5nvg5Ar%fengguang.wu@intel.com> (raw)
In-Reply-To: <1450184056-79851-4-git-send-email-puck.chen@hisilicon.com>
Hi Chen,
[auto build test WARNING on ljones-mfd/for-mfd-next]
[also build test WARNING on v4.4-rc5 next-20151214]
url: https://github.com/0day-ci/linux/commits/Chen-Feng/Add-Support-for-Hi6220-PMIC-Hi6553-MFD-Core/20151215-210113
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
coccinelle warnings: (new ones prefixed by >>)
>> drivers/mfd/hi655x-pmic.c:161:3-8: No need to set .owner here. The core will do it.
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:[~2015-12-15 13:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 12:54 [PATCH v3 0/5] Add Support for Hi6220 PMIC Hi6553 MFD Core Chen Feng
2015-12-15 12:54 ` [PATCH v3 1/5] doc: bindings: Add document for mfd hi665x PMIC Chen Feng
2015-12-15 12:54 ` [PATCH v3 2/5] doc: bindings: Document for hi655x regulator driver Chen Feng
2015-12-15 12:54 ` [PATCH v3 3/5] mfd: hi655x: Add hi665x pmic driver Chen Feng
2015-12-15 13:29 ` kbuild test robot [this message]
2015-12-15 13:29 ` [PATCH] mfd: hi655x: fix platform_no_drv_owner.cocci warnings kbuild test robot
2015-12-15 12:54 ` [PATCH v3 4/5] regulator: add regulator driver of hi655x PMIC Chen Feng
2015-12-16 19:16 ` Mark Brown
2015-12-17 3:18 ` chenfeng
2015-12-15 12:54 ` [PATCH v3 5/5] hisilicon/dts: Add hi655x pmic dts node Chen Feng
2015-12-17 3:27 ` chenfeng
2015-12-18 17:58 ` Mark Brown
2015-12-21 3:01 ` chenfeng
2015-12-21 6:20 ` chenfeng
2015-12-23 0:46 ` Mark Brown
2015-12-24 2:43 ` chenfeng
2015-12-22 16:08 ` Mark Brown
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=201512152147.S5nvg5Ar%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=dan.zhao@hisilicon.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kbuild-all@01.org \
--cc=kong.kongxinwei@hisilicon.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=peter.panshilin@hisilicon.com \
--cc=puck.chen@aliyun.com \
--cc=puck.chen@hisilicon.com \
--cc=qijiwen@hisilicon.com \
--cc=robh+dt@kernel.org \
--cc=saberlily.xia@hisilicon.com \
--cc=suzhuangluan@hisilicon.com \
--cc=w.f@huawei.com \
--cc=weidong2@hisilicon.com \
--cc=xuwei5@hisilicon.com \
--cc=xuyiping@hisilicon.com \
--cc=yudongbin@hisilicon.com \
--cc=z.liuxinliang@hisilicon.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
all inboxes | Powered by JetHome®