From: Stephen Boyd <sboyd@codeaurora.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Sergej Sawazki <sergej@taudac.com>,
kbuild-all@01.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH clk] clk: si5351: _si5351_clkout_reset_pll() can be static
Date: Thu, 28 Dec 2017 10:50:07 -0800 [thread overview]
Message-ID: <20171228185007.GR7997@codeaurora.org> (raw)
In-Reply-To: <20171227042513.GA56372@ivb42>
On 12/27, kbuild test robot wrote:
>
> Fixes: b26ff127c52c ("clk: si5351: Apply PLL soft reset before enabling the outputs")
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH clk] clk: si5351: _si5351_clkout_reset_pll() can be static
Date: Thu, 28 Dec 2017 10:50:07 -0800 [thread overview]
Message-ID: <20171228185007.GR7997@codeaurora.org> (raw)
In-Reply-To: <20171227042513.GA56372@ivb42>
On 12/27, kbuild test robot wrote:
>
> Fixes: b26ff127c52c ("clk: si5351: Apply PLL soft reset before enabling the outputs")
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-12-28 18:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-27 4:25 [clk:clk-next 136/143] drivers/clk/clk-si5351.c:906:6: sparse: symbol '_si5351_clkout_reset_pll' was not declared. Should it be static? kbuild test robot
2017-12-27 4:25 ` kbuild test robot
2017-12-27 4:25 ` [RFC PATCH clk] clk: si5351: _si5351_clkout_reset_pll() can be static kbuild test robot
2017-12-27 4:25 ` kbuild test robot
2017-12-28 18:50 ` Stephen Boyd [this message]
2017-12-28 18:50 ` Stephen Boyd
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=20171228185007.GR7997@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=sergej@taudac.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.