From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dou Liyang Subject: Re: linux-next: build warning after merge of the tip tree Date: Fri, 16 Mar 2018 14:04:08 +0800 Message-ID: <5b2382ce-c51d-38b5-5c9b-4386e603ac68@cn.fujitsu.com> References: <20180316163716.5525294f@canb.auug.org.au> <3b2889c6-3f0b-b0f4-d5a7-3b4cf5c5ef75@cn.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <3b2889c6-3f0b-b0f4-d5a7-3b4cf5c5ef75@cn.fujitsu.com> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: Stephen Rothwell , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra Cc: Linux-Next Mailing List , Linux Kernel Mailing List , Lai Jiangshan List-Id: linux-next.vger.kernel.org Archived-At: List-Archive: List-Post: Hi Stephen, At 03/16/2018 01:52 PM, Dou Liyang wrote: > Hi Stephen, > > At 03/16/2018 01:37 PM, Stephen Rothwell wrote: >> Hi all, >> >> After merging the tip tree, yesterday's linux-next build (x86_64 >> allnoconfig) >> produced this warning: >> >> kernel/cpu.c:129:13: warning: 'cpuhp_is_ap_state' defined but not used >> [-Wunused-function] >>   static bool cpuhp_is_ap_state(enum cpuhp_state state) >>               ^~~~~~~~~~~~~~~~~ >> > > Yes, Jiangshan has replaced it with cpuhp_hp_states. So it is obsolete, > it should be removed. > I made a mistake, It also be called by cpuhp_thread_fun() and cpuhp_issue_call(), let me have a look carefully. Thanks, dou. > Thanks, >     dou. >> Introduced by commit >> >>    17a2f1ced028 ("cpu/hotplug: Merge cpuhp_bp_states and >> cpuhp_ap_states") >>