From: kbuild test robot <lkp@intel.com>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: kbuild-all@01.org, mturquette@baylibre.com,
cw00.choi@samsung.com, lee.jones@linaro.org,
sboyd@codeaurora.org, myungjoo.ham@samsung.com,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 3/4] mfd: arizona: Switch to using clock driver for 32k clock
Date: Wed, 6 Jan 2016 00:19:56 +0800 [thread overview]
Message-ID: <201601060012.oyAzKzVL%fengguang.wu@intel.com> (raw)
In-Reply-To: <1452008502-3749-3-git-send-email-ckeepax@opensource.wolfsonmicro.com>
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
Hi Charles,
[auto build test WARNING on clk/clk-next]
[also build test WARNING on v4.4-rc8 next-20160105]
[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/Charles-Keepax/extcon-arizona-Remove-enable-disable-of-32k-clock/20160105-234658
base: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-next
config: x86_64-randconfig-x013-01041832 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All warnings (new ones prefixed by >>):
warning: (MFD_ARIZONA) selects COMMON_CLK_ARIZONA which has unmet direct dependencies (COMMON_CLK && MFD_ARIZONA)
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 25289 bytes --]
next prev parent reply other threads:[~2016-01-05 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 15:41 [PATCH 1/4] extcon: arizona: Remove enable/disable of 32k clock Charles Keepax
2016-01-05 15:41 ` [PATCH 2/4] clk: arizona: Add clock driver for the Arizona devices Charles Keepax
2016-01-06 1:45 ` Stephen Boyd
[not found] ` <1452008502-3749-1-git-send-email-ckeepax-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2016-01-05 15:41 ` [PATCH 3/4] mfd: arizona: Switch to using clock driver for 32k clock Charles Keepax
2016-01-05 16:19 ` kbuild test robot [this message]
2016-01-06 9:37 ` Charles Keepax
2016-01-05 16:23 ` kbuild test robot
2016-01-05 15:41 ` [PATCH 4/4] mfd: arizona: Add device tree binding documentation for new clock driver Charles Keepax
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=201601060012.oyAzKzVL%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=kbuild-all@01.org \
--cc=lee.jones@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=myungjoo.ham@samsung.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sboyd@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).