From: geert@linux-m68k.org (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 1/1] clk: bulk: add of_clk_bulk_get()
Date: Sun, 24 Sep 2017 10:05:36 +0200 [thread overview]
Message-ID: <CAMuHMdX5Sg+=DVDn9sgk5ikr5T8ygnHRCcrpPGEZPub0EDvbCw@mail.gmail.com> (raw)
In-Reply-To: <201709240941.1xKB0Rqm%fengguang.wu@intel.com>
On Sun, Sep 24, 2017 at 4:06 AM, kbuild test robot <lkp@intel.com> wrote:
> [auto build test ERROR on clk/clk-next]
> [also build test ERROR on v4.14-rc1 next-20170922]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>
> url: https://github.com/0day-ci/linux/commits/Dong-Aisheng/clk-bulk-add-of_clk_bulk_get/20170921-203645
> base: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-next
> config: sh-apsh4a3a_defconfig (attached as .config)
> compiler: sh4-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> make.cross ARCH=sh
>
> All errors (new ones prefixed by >>):
>
> In file included from arch/sh/kernel/setup.c:28:0:
>>> include/linux/clk.h:689:12: error: 'of_clk_bulk_get' defined but not used [-Werror=unused-function]
> static int of_clk_bulk_get(struct device_node *np, int num_clks,
> ^~~~~~~~~~~~~~~
> cc1: all warnings being treated as errors
>
> vim +/of_clk_bulk_get +689 include/linux/clk.h
>
> 681
> 682 #if defined(CONFIG_OF) && defined(CONFIG_COMMON_CLK)
> 683 int __must_check of_clk_bulk_get(struct device_node *np, int num_clks,
> 684 struct clk_bulk_data *clks);
> 685 struct clk *of_clk_get(struct device_node *np, int index);
> 686 struct clk *of_clk_get_by_name(struct device_node *np, const char *name);
> 687 struct clk *of_clk_get_from_provider(struct of_phandle_args *clkspec);
> 688 #else
> > 689 static int of_clk_bulk_get(struct device_node *np, int num_clks,
static inline
> 690 struct clk_bulk_data *clks)
> 691 {
> 692 return -ENOENT;
> 693 }
> 694
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2017-09-24 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 7:49 [PATCH V3 1/1] clk: bulk: add of_clk_bulk_get() Dong Aisheng
2017-09-24 2:06 ` kbuild test robot
2017-09-24 8:05 ` Geert Uytterhoeven [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='CAMuHMdX5Sg+=DVDn9sgk5ikr5T8ygnHRCcrpPGEZPub0EDvbCw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.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).