Re: [patch] ARM: qcom: silence an uninitialized variable warning

2016-04-14 Thread Dan Carpenter
On Thu, Apr 14, 2016 at 03:53:03AM +0200, Arnd Bergmann wrote: > On Wednesday 13 April 2016, Dan Carpenter wrote: > > It's harmless but, if "enable" isn't set, then we pass uninitialized > > values to qcom_coincell_chgr_config(). The values aren't used, but > > let's silence the warning anyway. >

Re: [patch] ARM: qcom: silence an uninitialized variable warning

2016-04-13 Thread Arnd Bergmann
On Wednesday 13 April 2016, Dan Carpenter wrote: > It's harmless but, if "enable" isn't set, then we pass uninitialized > values to qcom_coincell_chgr_config(). The values aren't used, but > let's silence the warning anyway. > > Signed-off-by: Dan Carpenter I haven't seen this warning in my tes

Re: [patch] ARM: qcom: silence an uninitialized variable warning

2016-04-13 Thread Tim Bird
On 04/12/2016 11:45 PM, Dan Carpenter wrote: > It's harmless but, if "enable" isn't set, then we pass uninitialized > values to qcom_coincell_chgr_config(). The values aren't used, but > let's silence the warning anyway. > > Signed-off-by: Dan Carpenter > > diff --git a/drivers/misc/qcom-coin

[patch] ARM: qcom: silence an uninitialized variable warning

2016-04-12 Thread Dan Carpenter
It's harmless but, if "enable" isn't set, then we pass uninitialized values to qcom_coincell_chgr_config(). The values aren't used, but let's silence the warning anyway. Signed-off-by: Dan Carpenter diff --git a/drivers/misc/qcom-coincell.c b/drivers/misc/qcom-coincell.c index 7b4a2da..829a61d