public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Kaehlcke <mka@chromium.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>,
	Yang A Fang <yang.a.fang@intel.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	Douglas Anderson <dianders@chromium.org>
Subject: Re: [alsa-devel] [PATCH] ASoC: cht_bsw_max98090_ti: Remove unused function cht_get_codec_dai()
Date: Tue, 23 May 2017 12:32:39 -0700	[thread overview]
Message-ID: <20170523193239.GP141096@google.com> (raw)
In-Reply-To: <6f941eb4-04b9-89ea-a791-c65c939581cf@linux.intel.com>

Hi Pierre-Louis,

El Tue, May 23, 2017 at 12:25:17PM -0700 Pierre-Louis Bossart ha dit:

> On 5/23/17 12:05 PM, Matthias Kaehlcke wrote:
> >Looks like the function has never been used since it was added by commit
> >17119a465706 ("ASoC: Intel: Add Cherrytrail & Braswell machine driver
> >cht_bsw_max98090_ti"). Removing it fixes the following warning when
> >building with clang:
> >
> >sound/soc/intel/boards/cht_bsw_max98090_ti.c:42:35: error: unused
> >    function 'cht_get_codec_dai' [-Werror,-Wunused-function]
> 
> Fine but it'll have to be re-added when I finally find the time to
> support Baytrail with this driver.

If you have plans to add the code in a nearish future it is probably
not worth to do the removal, unless the maintainers think otherwise.

> >Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
> >---
> > sound/soc/intel/boards/cht_bsw_max98090_ti.c | 12 ------------
> > 1 file changed, 12 deletions(-)
> >
> >diff --git a/sound/soc/intel/boards/cht_bsw_max98090_ti.c b/sound/soc/intel/boards/cht_bsw_max98090_ti.c
> >index 742bc0d4e681..20755ecc7f9e 100644
> >--- a/sound/soc/intel/boards/cht_bsw_max98090_ti.c
> >+++ b/sound/soc/intel/boards/cht_bsw_max98090_ti.c
> >@@ -39,18 +39,6 @@ struct cht_mc_private {
> > 	bool ts3a227e_present;
> > };
> >
> >-static inline struct snd_soc_dai *cht_get_codec_dai(struct snd_soc_card *card)
> >-{
> >-	struct snd_soc_pcm_runtime *rtd;
> >-
> >-	list_for_each_entry(rtd, &card->rtd_list, list) {
> >-		if (!strncmp(rtd->codec_dai->name, CHT_CODEC_DAI,
> >-			     strlen(CHT_CODEC_DAI)))
> >-			return rtd->codec_dai;
> >-	}
> >-	return NULL;
> >-}
> >-
> > static const struct snd_soc_dapm_widget cht_dapm_widgets[] = {
> > 	SND_SOC_DAPM_HP("Headphone", NULL),
> > 	SND_SOC_DAPM_MIC("Headset Mic", NULL),
> >
> 

  reply	other threads:[~2017-05-23 19:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23 19:05 [PATCH] ASoC: cht_bsw_max98090_ti: Remove unused function cht_get_codec_dai() Matthias Kaehlcke
2017-05-23 19:25 ` [alsa-devel] " Pierre-Louis Bossart
2017-05-23 19:32   ` Matthias Kaehlcke [this message]
2017-05-23 19:49     ` Pierre-Louis Bossart
2017-05-24 17:42 ` Applied "ASoC: cht_bsw_max98090_ti: Remove unused function cht_get_codec_dai()" to the asoc tree Mark Brown

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=20170523193239.GP141096@google.com \
    --to=mka@chromium.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=dianders@chromium.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.com \
    --cc=yang.a.fang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox