From: Zhang Rui <rui.zhang@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Amit Kucheria <amit.kucheria@linaro.org>,
Leo Yan <leo.yan@linaro.org>
Subject: Re: linux-next: build warning after merge of the thermal tree
Date: Wed, 24 Aug 2016 15:56:13 +0800 [thread overview]
Message-ID: <1472025373.2682.42.camel@intel.com> (raw)
In-Reply-To: <20160824133833.3e92892a@canb.auug.org.au>
On 三, 2016-08-24 at 13:38 +1000, Stephen Rothwell wrote:
> Hi Zhang,
>
> After merging the thermal tree, today's linux-next build (powerpc
> allyesconfig) produced this warning:
>
> warning: (HISI_THERMAL) selects STUB_CLK_HI6220 which has unmet
> direct dependencies (COMMON_CLK && COMMON_CLK_HI6220 && MAILBOX)
>
> Introduced by commit
>
> 5f63581ce68e ("thermal: hisilicon: Add dependency on the clock
> driver to allow frequency scaling")
>
> BTW: That commit message does not match the change (which adds a
> "select" not a "depends on".
>
Right, thanks for reporting the issue. Patch dropped from thermal -next
tree.
thanks,
rui
next prev parent reply other threads:[~2016-08-24 7:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 3:38 linux-next: build warning after merge of the thermal tree Stephen Rothwell
2016-08-24 7:56 ` Zhang Rui [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-01 0:52 Stephen Rothwell
2019-04-30 3:48 Stephen Rothwell
2019-10-21 23:23 Stephen Rothwell
2019-10-22 9:50 ` Amit Kucheria
2019-10-22 11:18 ` Stephen Rothwell
2019-10-24 7:26 ` Amit Kucheria
2019-10-29 9:05 ` Geert Uytterhoeven
2020-03-02 23:42 Stephen Rothwell
2020-03-03 0:17 ` Daniel Lezcano
2020-10-27 0:34 Stephen Rothwell
2025-05-02 9:07 Stephen Rothwell
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=1472025373.2682.42.camel@intel.com \
--to=rui.zhang@intel.com \
--cc=amit.kucheria@linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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