From: kbuild test robot <lkp@intel.com>
To: Paul Osmialowski <newchief@king.net.pl>
Cc: kbuild-all@01.org, Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Paul Osmialowski <pawelo@king.net.pl>
Subject: Re: [PATCH v2] clk: add devm_of_clk_get() and devm_of_clk_get_by_name() functions
Date: Wed, 30 Sep 2015 17:13:42 +0800 [thread overview]
Message-ID: <201509301715.kkzE1BaC%fengguang.wu@intel.com> (raw)
In-Reply-To: <1443599212-31698-2-git-send-email-newchief@king.net.pl>
[-- Attachment #1: Type: text/plain, Size: 2335 bytes --]
Hi Paul,
[auto build test results on v4.3-rc3 -- if it's inappropriate base, please ignore]
config: arm-sa1100 (attached as .config)
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 4b38631724b90dc5a717a4467cbf9377e3bf9af2
# save the attached .config to linux build tree
make.cross ARCH=arm
All error/warnings (new ones prefixed by >>):
>> drivers/clk/clk-devres.c:39:13: error: redefinition of 'devm_of_clk_get'
struct clk *devm_of_clk_get(struct device *dev, struct device_node *np,
^
In file included from drivers/clk/clk-devres.c:7:0:
include/linux/clk.h:539:27: note: previous definition of 'devm_of_clk_get' was here
static inline struct clk *devm_of_clk_get(struct device *dev,
^
>> drivers/clk/clk-devres.c:60:13: error: redefinition of 'devm_of_clk_get_by_name'
struct clk *devm_of_clk_get_by_name(struct device *dev, struct device_node *np,
^
In file included from drivers/clk/clk-devres.c:7:0:
include/linux/clk.h:545:27: note: previous definition of 'devm_of_clk_get_by_name' was here
static inline struct clk *devm_of_clk_get_by_name(struct device *dev,
^
vim +/devm_of_clk_get +39 drivers/clk/clk-devres.c
33 return clk;
34 }
35 EXPORT_SYMBOL(devm_clk_get);
36
37 #ifdef CONFIG_OF
38
> 39 struct clk *devm_of_clk_get(struct device *dev, struct device_node *np,
40 int index)
41 {
42 struct clk **ptr, *clk;
43
44 ptr = devres_alloc(devm_clk_release, sizeof(*ptr), GFP_KERNEL);
45 if (!ptr)
46 return ERR_PTR(-ENOMEM);
47
48 clk = of_clk_get(np, index);
49 if (!IS_ERR(clk)) {
50 *ptr = clk;
51 devres_add(dev, ptr);
52 } else {
53 devres_free(ptr);
54 }
55
56 return clk;
57 }
58 EXPORT_SYMBOL(devm_of_clk_get);
59
> 60 struct clk *devm_of_clk_get_by_name(struct device *dev, struct device_node *np,
61 const char *name)
62 {
63 struct clk **ptr, *clk;
---
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: 21715 bytes --]
prev parent reply other threads:[~2015-09-30 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 7:46 [PATCH 0/1] " Paul Osmialowski
2015-09-30 7:46 ` [PATCH v2] clk: " Paul Osmialowski
2015-09-30 9:13 ` kbuild test robot [this message]
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=201509301715.kkzE1BaC%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mturquette@baylibre.com \
--cc=newchief@king.net.pl \
--cc=pawelo@king.net.pl \
--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
all inboxes | Powered by JetHome®