From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751611AbdFIHFI (ORCPT ); Fri, 9 Jun 2017 03:05:08 -0400 Received: from mx2.suse.de ([195.135.220.15]:58575 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751522AbdFIHFG (ORCPT ); Fri, 9 Jun 2017 03:05:06 -0400 Date: Fri, 09 Jun 2017 09:05:04 +0200 Message-ID: From: Takashi Iwai To: Vinod Koul Cc: Matthias Kaehlcke , Liam Girdwood , Mark Brown , Jaroslav Kysela , alsa-devel@alsa-project.org, Douglas Anderson , linux-kernel@vger.kernel.org Subject: Re: [PATCH] ASoC: Intel: sst: Remove unused function sst_restore_shim64() In-Reply-To: <20170609034004.GR2885@localhost> References: <20170523001258.81618-1-mka@chromium.org> <20170609034004.GR2885@localhost> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.2 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 09 Jun 2017 05:40:04 +0200, Vinod Koul wrote: > > On Wed, Jun 07, 2017 at 11:40:19PM +0200, Takashi Iwai wrote: > > On Tue, 23 May 2017 02:12:58 +0200, > > Matthias Kaehlcke wrote: > > > > > > Looks like the function has never been used since it was added by commit > > > b0d94acd634a ("ASoC: Intel: mrfld - add shim save restore"). Removing it > > > fixes the following warning when building with clang: > > > > > > sound/soc/intel/atom/sst/sst.c:360:20: error: unused function > > > 'sst_restore_shim64' [-Werror,-Wunused-function] > > > > > > Signed-off-by: Matthias Kaehlcke > > > > Hmm, although this patch was already merged, I now think this is > > rather a bug. If the restore is never executed, why the counterpart, > > sst_save_shim64() is required at all at runtime suspend? > > > > Vinod? > > It was supposed to be required in early BYT boards. I do not seem to recall > why the call to sst_restore_shim64 was removed from resume routine, it was > there when we added it and due to file move git log is useless. > > Any idea how to get changes to file before the file was moved? Try to pass --follow option to git log. sst_save_shim64() and sst_restore_shim64() were introduced at b0d94acd634a5cff7fe5fc46131a23997e8d0f60 but not actually used. The call of sst_save_shim64() was added in 336cfbb05edf7b122ea927dad6c746608723eb25 but already without the counter-part for restore. thanks, Takashi