linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] ASoC: codec: wm9860: avoid maybe-uninitialized warning
@ 2017-04-19 17:04 Arnd Bergmann
  2017-04-20  6:48 ` Daniel Baluta
                   ` (2 more replies)
  0 siblings, 3 replies; 8+ messages in thread
From: Arnd Bergmann @ 2017-04-19 17:04 UTC (permalink / raw)
  To: Liam Girdwood, Mark Brown
  Cc: Arnd Bergmann, Charles Keepax, Daniel Baluta, patches,
	alsa-devel, linux-kernel

The new PLL configuration code triggers a harmless warning:

sound/soc/codecs/wm8960.c: In function 'wm8960_configure_clocking':
sound/soc/codecs/wm8960.c:735:3: error: 'best_freq_out' may be used uninitialized in this function [-Werror=maybe-uninitialized]
   wm8960_set_pll(codec, freq_in, best_freq_out);
   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
sound/soc/codecs/wm8960.c:699:12: note: 'best_freq_out' was declared here

I think the warning was introduced by Daniel's bugfix. I've come up
with a way to simplify the code in a way that is more readable to
both humans and to gcc, which gets us rid of the warning.

Fixes: 84fdc00d519f ("ASoC: codec: wm9860: Refactor PLL out freq search")
Fixes: 303e8954af8d ("ASoC: codec: wm8960: Stop when a matching PLL freq is found")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
---
 sound/soc/codecs/wm8960.c | 25 ++++++++-----------------
 1 file changed, 8 insertions(+), 17 deletions(-)

diff --git a/sound/soc/codecs/wm8960.c b/sound/soc/codecs/wm8960.c
index ace69da97cb8..ba0f80504c6b 100644
--- a/sound/soc/codecs/wm8960.c
+++ b/sound/soc/codecs/wm8960.c
@@ -696,14 +696,12 @@ int wm8960_configure_pll(struct snd_soc_codec *codec, int freq_in,
 {
 	struct wm8960_priv *wm8960 = snd_soc_codec_get_drvdata(codec);
 	int sysclk, bclk, lrclk, freq_out;
-	int diff, best_freq_out;
+	int diff;
 	int i, j, k;
 
 	bclk = wm8960->bclk;
 	lrclk = wm8960->lrclk;
 
-	*bclk_idx = -1;
-
 	for (i = 0; i < ARRAY_SIZE(sysclk_divs); ++i) {
 		if (sysclk_divs[i] == -1)
 			continue;
@@ -720,22 +718,14 @@ int wm8960_configure_pll(struct snd_soc_codec *codec, int freq_in,
 					*sysclk_idx = i;
 					*dac_idx = j;
 					*bclk_idx = k;
-					best_freq_out = freq_out;
-					break;
+					return freq_out;
 				}
 			}
-			if (k != ARRAY_SIZE(bclk_divs))
-				break;
 		}
-		if (j != ARRAY_SIZE(dac_divs))
-			break;
 	}
-
-	if (*bclk_idx != -1)
-		wm8960_set_pll(codec, freq_in, best_freq_out);
-
-	return *bclk_idx;
+	return -EINVAL;
 }
+
 static int wm8960_configure_clocking(struct snd_soc_codec *codec)
 {
 	struct wm8960_priv *wm8960 = snd_soc_codec_get_drvdata(codec);
@@ -783,11 +773,12 @@ static int wm8960_configure_clocking(struct snd_soc_codec *codec)
 		}
 	}
 
-	ret = wm8960_configure_pll(codec, freq_in, &i, &j, &k);
-	if (ret < 0) {
+	freq_out = wm8960_configure_pll(codec, freq_in, &i, &j, &k);
+	if (freq_out < 0) {
 		dev_err(codec->dev, "failed to configure clock via PLL\n");
-		return -EINVAL;
+		return freq_out;
 	}
+	wm8960_set_pll(codec, freq_in, freq_out);
 
 configure_clock:
 	/* configure sysclk clock */
-- 
2.9.0

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH] ASoC: codec: wm9860: avoid maybe-uninitialized warning
  2017-04-19 17:04 [PATCH] ASoC: codec: wm9860: avoid maybe-uninitialized warning Arnd Bergmann
@ 2017-04-20  6:48 ` Daniel Baluta
  2017-04-20  7:44   ` Arnd Bergmann
  2017-04-20  9:07 ` Charles Keepax
  2017-05-14 10:05 ` Mark Brown
  2 siblings, 1 reply; 8+ messages in thread
From: Daniel Baluta @ 2017-04-20  6:48 UTC (permalink / raw)
  To: Arnd Bergmann
  Cc: Liam Girdwood, Mark Brown, Charles Keepax, Daniel Baluta,
	patches, alsa-devel, Linux Kernel Mailing List

Hi Arnd,

On Wed, Apr 19, 2017 at 8:04 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> The new PLL configuration code triggers a harmless warning:
>
> sound/soc/codecs/wm8960.c: In function 'wm8960_configure_clocking':
> sound/soc/codecs/wm8960.c:735:3: error: 'best_freq_out' may be used uninitialized in this function [-Werror=maybe-uninitialized]
>    wm8960_set_pll(codec, freq_in, best_freq_out);
>    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> sound/soc/codecs/wm8960.c:699:12: note: 'best_freq_out' was declared here
>
> I think the warning was introduced by Daniel's bugfix. I've come up
> with a way to simplify the code in a way that is more readable to
> both humans and to gcc, which gets us rid of the warning.

I've struggled with this kind of warning when reworking wm8960
bitclock computation.

Anyhow, for this exact patch the warning didn't showed up.

I used:

gcc version 6.2.1 20161016 (Linaro GCC 6.2-2016.11)

My next patch:

https://patchwork.kernel.org/patch/9666921/ [1]

which is under review, had the issue you mention (in v1)

https://lkml.org/lkml/2017/4/5/246

but I initialized best_freq_out with 0 to get rid of the problem.

>
> Fixes: 84fdc00d519f ("ASoC: codec: wm9860: Refactor PLL out freq search")
> Fixes: 303e8954af8d ("ASoC: codec: wm8960: Stop when a matching PLL freq is found")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
>  sound/soc/codecs/wm8960.c | 25 ++++++++-----------------
>  1 file changed, 8 insertions(+), 17 deletions(-)
>
> diff --git a/sound/soc/codecs/wm8960.c b/sound/soc/codecs/wm8960.c
> index ace69da97cb8..ba0f80504c6b 100644
> --- a/sound/soc/codecs/wm8960.c
> +++ b/sound/soc/codecs/wm8960.c
> @@ -696,14 +696,12 @@ int wm8960_configure_pll(struct snd_soc_codec *codec, int freq_in,
>  {
>         struct wm8960_priv *wm8960 = snd_soc_codec_get_drvdata(codec);
>         int sysclk, bclk, lrclk, freq_out;
> -       int diff, best_freq_out;
> +       int diff;
>         int i, j, k;
>
>         bclk = wm8960->bclk;
>         lrclk = wm8960->lrclk;
>
> -       *bclk_idx = -1;
> -
>         for (i = 0; i < ARRAY_SIZE(sysclk_divs); ++i) {
>                 if (sysclk_divs[i] == -1)
>                         continue;
> @@ -720,22 +718,14 @@ int wm8960_configure_pll(struct snd_soc_codec *codec, int freq_in,
>                                         *sysclk_idx = i;
>                                         *dac_idx = j;
>                                         *bclk_idx = k;
> -                                       best_freq_out = freq_out;
> -                                       break;
> +                                       return freq_out;
>                                 }
>                         }
> -                       if (k != ARRAY_SIZE(bclk_divs))
> -                               break;
>                 }
> -               if (j != ARRAY_SIZE(dac_divs))
> -                       break;
>         }
> -
> -       if (*bclk_idx != -1)
> -               wm8960_set_pll(codec, freq_in, best_freq_out);

I think the compiler is tricked into thinking that best_freq_out might
be uninitialized. Notice
that each time *bclk_idx is assigned a value (which is always >=0) we
also initialize best_freq_out.

> -
> -       return *bclk_idx;
> +       return -EINVAL;
>  }
> +
>  static int wm8960_configure_clocking(struct snd_soc_codec *codec)
>  {
>         struct wm8960_priv *wm8960 = snd_soc_codec_get_drvdata(codec);
> @@ -783,11 +773,12 @@ static int wm8960_configure_clocking(struct snd_soc_codec *codec)
>                 }
>         }
>
> -       ret = wm8960_configure_pll(codec, freq_in, &i, &j, &k);
> -       if (ret < 0) {
> +       freq_out = wm8960_configure_pll(codec, freq_in, &i, &j, &k);
> +       if (freq_out < 0) {
>                 dev_err(codec->dev, "failed to configure clock via PLL\n");
> -               return -EINVAL;
> +               return freq_out;
>         }
> +       wm8960_set_pll(codec, freq_in, freq_out);
>
>  configure_clock:
>         /* configure sysclk clock */

Your idea looks good, will need to rework my follow up patch on it:

https://patchwork.kernel.org/patch/9666921/

thanks,
Daniel.

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH] ASoC: codec: wm9860: avoid maybe-uninitialized warning
  2017-04-20  6:48 ` Daniel Baluta
@ 2017-04-20  7:44   ` Arnd Bergmann
  2017-04-20  8:22     ` Daniel Baluta
  2017-04-20 19:48     ` Mark Brown
  0 siblings, 2 replies; 8+ messages in thread
From: Arnd Bergmann @ 2017-04-20  7:44 UTC (permalink / raw)
  To: Daniel Baluta
  Cc: Liam Girdwood, Mark Brown, Charles Keepax, Daniel Baluta,
	patches, alsa-devel, Linux Kernel Mailing List

On Thu, Apr 20, 2017 at 8:48 AM, Daniel Baluta <daniel.baluta@gmail.com> wrote:
> Hi Arnd,
>
> On Wed, Apr 19, 2017 at 8:04 PM, Arnd Bergmann <arnd@arndb.de> wrote:
>> The new PLL configuration code triggers a harmless warning:
>>
>> sound/soc/codecs/wm8960.c: In function 'wm8960_configure_clocking':
>> sound/soc/codecs/wm8960.c:735:3: error: 'best_freq_out' may be used uninitialized in this function [-Werror=maybe-uninitialized]
>>    wm8960_set_pll(codec, freq_in, best_freq_out);
>>    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> sound/soc/codecs/wm8960.c:699:12: note: 'best_freq_out' was declared here
>>
>> I think the warning was introduced by Daniel's bugfix. I've come up
>> with a way to simplify the code in a way that is more readable to
>> both humans and to gcc, which gets us rid of the warning.
>
> I've struggled with this kind of warning when reworking wm8960
> bitclock computation.
>
> Anyhow, for this exact patch the warning didn't showed up.
>
> I used:
>
> gcc version 6.2.1 20161016 (Linaro GCC 6.2-2016.11)

I'm using gcc-7.0.1 here, which overall has better warnings for
-Wmaybe-uninitialized
than older versions, but sometimes also finds new false positives.

> My next patch:
>
> https://patchwork.kernel.org/patch/9666921/ [1]
>
> which is under review, had the issue you mention (in v1)
>
> https://lkml.org/lkml/2017/4/5/246
>
> but I initialized best_freq_out with 0 to get rid of the problem.

I try hard not to do that, because it can hide real problems in case the
code gets modified further to actually have an uninitialized use that we
would otherwise get a warning for.

>> @@ -720,22 +718,14 @@ int wm8960_configure_pll(struct snd_soc_codec *codec, int freq_in,
>>                                         *sysclk_idx = i;
>>                                         *dac_idx = j;
>>                                         *bclk_idx = k;
>> -                                       best_freq_out = freq_out;
>> -                                       break;
>> +                                       return freq_out;
>>                                 }
>>                         }
>> -                       if (k != ARRAY_SIZE(bclk_divs))
>> -                               break;
>>                 }
>> -               if (j != ARRAY_SIZE(dac_divs))
>> -                       break;
>>         }
>> -
>> -       if (*bclk_idx != -1)
>> -               wm8960_set_pll(codec, freq_in, best_freq_out);
>
> I think the compiler is tricked into thinking that best_freq_out might
> be uninitialized. Notice
> that each time *bclk_idx is assigned a value (which is always >=0) we
> also initialize best_freq_out.

Right. This is probably the result of one of two things that
prevent the compiler from figuring it out:

a) bclk_idx being an indirect pointer might cause the compiler to
    decide that another operation might overwrite it, e.g. if it points
    to the same location as one of the other pointers.

b) The flow analysis might just get too tricky, so when gcc gives
    up trying to work out whether the assignment has happened
    at least once for the two variables, it concludes that it doesn't
    know, without seeing that the answer is always the same for
    both of them.

>> @@ -783,11 +773,12 @@ static int wm8960_configure_clocking(struct snd_soc_codec *codec)
>>                 }
>>         }
>>
>> -       ret = wm8960_configure_pll(codec, freq_in, &i, &j, &k);
>> -       if (ret < 0) {
>> +       freq_out = wm8960_configure_pll(codec, freq_in, &i, &j, &k);
>> +       if (freq_out < 0) {
>>                 dev_err(codec->dev, "failed to configure clock via PLL\n");
>> -               return -EINVAL;
>> +               return freq_out;
>>         }
>> +       wm8960_set_pll(codec, freq_in, freq_out);
>>
>>  configure_clock:
>>         /* configure sysclk clock */
>
> Your idea looks good, will need to rework my follow up patch on it:
>
> https://patchwork.kernel.org/patch/9666921/

Ok. Or feel free to fold my patch into yours if that makes it easier for you.

     Arnd

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH] ASoC: codec: wm9860: avoid maybe-uninitialized warning
  2017-04-20  7:44   ` Arnd Bergmann
@ 2017-04-20  8:22     ` Daniel Baluta
  2017-04-20 19:48     ` Mark Brown
  1 sibling, 0 replies; 8+ messages in thread
From: Daniel Baluta @ 2017-04-20  8:22 UTC (permalink / raw)
  To: Arnd Bergmann
  Cc: Liam Girdwood, Mark Brown, Charles Keepax, Daniel Baluta,
	patches, alsa-devel, Linux Kernel Mailing List

On Thu, Apr 20, 2017 at 10:44 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> On Thu, Apr 20, 2017 at 8:48 AM, Daniel Baluta <daniel.baluta@gmail.com> wrote:
>> Hi Arnd,
>>
>> On Wed, Apr 19, 2017 at 8:04 PM, Arnd Bergmann <arnd@arndb.de> wrote:
>>> The new PLL configuration code triggers a harmless warning:
>>>
>>> sound/soc/codecs/wm8960.c: In function 'wm8960_configure_clocking':
>>> sound/soc/codecs/wm8960.c:735:3: error: 'best_freq_out' may be used uninitialized in this function [-Werror=maybe-uninitialized]
>>>    wm8960_set_pll(codec, freq_in, best_freq_out);
>>>    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> sound/soc/codecs/wm8960.c:699:12: note: 'best_freq_out' was declared here
>>>
>>> I think the warning was introduced by Daniel's bugfix. I've come up
>>> with a way to simplify the code in a way that is more readable to
>>> both humans and to gcc, which gets us rid of the warning.
>>
>> I've struggled with this kind of warning when reworking wm8960
>> bitclock computation.
>>
>> Anyhow, for this exact patch the warning didn't showed up.
>>
>> I used:
>>
>> gcc version 6.2.1 20161016 (Linaro GCC 6.2-2016.11)
>
> I'm using gcc-7.0.1 here, which overall has better warnings for
> -Wmaybe-uninitialized
> than older versions, but sometimes also finds new false positives.
>
>> My next patch:
>>
>> https://patchwork.kernel.org/patch/9666921/ [1]
>>
>> which is under review, had the issue you mention (in v1)
>>
>> https://lkml.org/lkml/2017/4/5/246
>>
>> but I initialized best_freq_out with 0 to get rid of the problem.
>
> I try hard not to do that, because it can hide real problems in case the
> code gets modified further to actually have an uninitialized use that we
> would otherwise get a warning for.
>
>>> @@ -720,22 +718,14 @@ int wm8960_configure_pll(struct snd_soc_codec *codec, int freq_in,
>>>                                         *sysclk_idx = i;
>>>                                         *dac_idx = j;
>>>                                         *bclk_idx = k;
>>> -                                       best_freq_out = freq_out;
>>> -                                       break;
>>> +                                       return freq_out;
>>>                                 }
>>>                         }
>>> -                       if (k != ARRAY_SIZE(bclk_divs))
>>> -                               break;
>>>                 }
>>> -               if (j != ARRAY_SIZE(dac_divs))
>>> -                       break;
>>>         }
>>> -
>>> -       if (*bclk_idx != -1)
>>> -               wm8960_set_pll(codec, freq_in, best_freq_out);
>>
>> I think the compiler is tricked into thinking that best_freq_out might
>> be uninitialized. Notice
>> that each time *bclk_idx is assigned a value (which is always >=0) we
>> also initialize best_freq_out.
>
> Right. This is probably the result of one of two things that
> prevent the compiler from figuring it out:
>
> a) bclk_idx being an indirect pointer might cause the compiler to
>     decide that another operation might overwrite it, e.g. if it points
>     to the same location as one of the other pointers.
>
> b) The flow analysis might just get too tricky, so when gcc gives
>     up trying to work out whether the assignment has happened
>     at least once for the two variables, it concludes that it doesn't
>     know, without seeing that the answer is always the same for
>     both of them.
>
>>> @@ -783,11 +773,12 @@ static int wm8960_configure_clocking(struct snd_soc_codec *codec)
>>>                 }
>>>         }
>>>
>>> -       ret = wm8960_configure_pll(codec, freq_in, &i, &j, &k);
>>> -       if (ret < 0) {
>>> +       freq_out = wm8960_configure_pll(codec, freq_in, &i, &j, &k);
>>> +       if (freq_out < 0) {
>>>                 dev_err(codec->dev, "failed to configure clock via PLL\n");
>>> -               return -EINVAL;
>>> +               return freq_out;
>>>         }
>>> +       wm8960_set_pll(codec, freq_in, freq_out);
>>>
>>>  configure_clock:
>>>         /* configure sysclk clock */
>>
>> Your idea looks good, will need to rework my follow up patch on it:
>>
>> https://patchwork.kernel.org/patch/9666921/
>
> Ok. Or feel free to fold my patch into yours if that makes it easier for you.

Great! I will fold your patch into my changes.

thanks Arnd!

Daniel.

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH] ASoC: codec: wm9860: avoid maybe-uninitialized warning
  2017-04-19 17:04 [PATCH] ASoC: codec: wm9860: avoid maybe-uninitialized warning Arnd Bergmann
  2017-04-20  6:48 ` Daniel Baluta
@ 2017-04-20  9:07 ` Charles Keepax
  2017-05-14 10:05 ` Mark Brown
  2 siblings, 0 replies; 8+ messages in thread
From: Charles Keepax @ 2017-04-20  9:07 UTC (permalink / raw)
  To: Arnd Bergmann
  Cc: Liam Girdwood, Mark Brown, Daniel Baluta, patches, alsa-devel,
	linux-kernel

On Wed, Apr 19, 2017 at 07:04:20PM +0200, Arnd Bergmann wrote:
> The new PLL configuration code triggers a harmless warning:
> 
> sound/soc/codecs/wm8960.c: In function 'wm8960_configure_clocking':
> sound/soc/codecs/wm8960.c:735:3: error: 'best_freq_out' may be used uninitialized in this function [-Werror=maybe-uninitialized]
>    wm8960_set_pll(codec, freq_in, best_freq_out);
>    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> sound/soc/codecs/wm8960.c:699:12: note: 'best_freq_out' was declared here
> 
> I think the warning was introduced by Daniel's bugfix. I've come up
> with a way to simplify the code in a way that is more readable to
> both humans and to gcc, which gets us rid of the warning.
> 
> Fixes: 84fdc00d519f ("ASoC: codec: wm9860: Refactor PLL out freq search")
> Fixes: 303e8954af8d ("ASoC: codec: wm8960: Stop when a matching PLL freq is found")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---

Acked-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>

Thanks,
Charles

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH] ASoC: codec: wm9860: avoid maybe-uninitialized warning
  2017-04-20  7:44   ` Arnd Bergmann
  2017-04-20  8:22     ` Daniel Baluta
@ 2017-04-20 19:48     ` Mark Brown
  1 sibling, 0 replies; 8+ messages in thread
From: Mark Brown @ 2017-04-20 19:48 UTC (permalink / raw)
  To: Arnd Bergmann
  Cc: Daniel Baluta, Liam Girdwood, Charles Keepax, Daniel Baluta,
	patches, alsa-devel, Linux Kernel Mailing List

[-- Attachment #1: Type: text/plain, Size: 600 bytes --]

On Thu, Apr 20, 2017 at 09:44:28AM +0200, Arnd Bergmann wrote:
> On Thu, Apr 20, 2017 at 8:48 AM, Daniel Baluta <daniel.baluta@gmail.com> wrote:
> > On Wed, Apr 19, 2017 at 8:04 PM, Arnd Bergmann <arnd@arndb.de> wrote:

> > gcc version 6.2.1 20161016 (Linaro GCC 6.2-2016.11)

> I'm using gcc-7.0.1 here, which overall has better warnings for
> -Wmaybe-uninitialized
> than older versions, but sometimes also finds new false positives.

FWIW the PLL stuff has typically been really good at generating false
positives with older versions of GCC for some reason, this driver is a
bit different though.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH] ASoC: codec: wm9860: avoid maybe-uninitialized warning
  2017-04-19 17:04 [PATCH] ASoC: codec: wm9860: avoid maybe-uninitialized warning Arnd Bergmann
  2017-04-20  6:48 ` Daniel Baluta
  2017-04-20  9:07 ` Charles Keepax
@ 2017-05-14 10:05 ` Mark Brown
  2017-05-15 14:03   ` Arnd Bergmann
  2 siblings, 1 reply; 8+ messages in thread
From: Mark Brown @ 2017-05-14 10:05 UTC (permalink / raw)
  To: Arnd Bergmann
  Cc: Liam Girdwood, Charles Keepax, Daniel Baluta, patches,
	alsa-devel, linux-kernel

[-- Attachment #1: Type: text/plain, Size: 192 bytes --]

On Wed, Apr 19, 2017 at 07:04:20PM +0200, Arnd Bergmann wrote:
> The new PLL configuration code triggers a harmless warning:

This doens't apply against current code, please check and resend.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [PATCH] ASoC: codec: wm9860: avoid maybe-uninitialized warning
  2017-05-14 10:05 ` Mark Brown
@ 2017-05-15 14:03   ` Arnd Bergmann
  0 siblings, 0 replies; 8+ messages in thread
From: Arnd Bergmann @ 2017-05-15 14:03 UTC (permalink / raw)
  To: Mark Brown
  Cc: Liam Girdwood, Charles Keepax, Daniel Baluta, patches,
	alsa-devel, Linux Kernel Mailing List

On Sun, May 14, 2017 at 12:05 PM, Mark Brown <broonie@kernel.org> wrote:
> On Wed, Apr 19, 2017 at 07:04:20PM +0200, Arnd Bergmann wrote:
>> The new PLL configuration code triggers a harmless warning:
>
> This doens't apply against current code, please check and resend.

I can confirm that you have already merged Daniel's updated version,
and that this addresses the problem.

       Arnd

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2017-05-15 14:03 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-04-19 17:04 [PATCH] ASoC: codec: wm9860: avoid maybe-uninitialized warning Arnd Bergmann
2017-04-20  6:48 ` Daniel Baluta
2017-04-20  7:44   ` Arnd Bergmann
2017-04-20  8:22     ` Daniel Baluta
2017-04-20 19:48     ` Mark Brown
2017-04-20  9:07 ` Charles Keepax
2017-05-14 10:05 ` Mark Brown
2017-05-15 14:03   ` Arnd Bergmann

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).