MIME-version: 1.0
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: 8BIT
Message-id: <53BE207A.8020800@samsung.com>
Date: Thu, 10 Jul 2014 14:11:22 +0900
From: Joonyoung Shim <jy0922.shim@samsung.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101
 Thunderbird/24.2.0
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Sachin Kamat <spk.linux@gmail.com>
Cc: Linux USB Mailing List <linux-usb@vger.kernel.org>,
        open list <linux-kernel@vger.kernel.org>,
        Marek Szyprowski <m.szyprowski@samsung.com>,
        Mark Brown <broonie@linaro.org>, tobetter@gmail.com
Subject: Re: [PATCH 1/3] usb: usb3503: fix build warning
References: <1404966228-29133-1-git-send-email-jy0922.shim@samsung.com>
 <CAK5sBcFKOc-_aGuC8QQu_NHc67AfZGz0MUeURqVr8P6K3Zzzmg@mail.gmail.com>
 <20140710050539.GD14064@kroah.com>
In-reply-to: <20140710050539.GD14064@kroah.com>
DLP-Filter: Pass
Sender: linux-kernel-owner@vger.kernel.org

On 07/10/2014 02:05 PM, Greg Kroah-Hartman wrote:
> On Thu, Jul 10, 2014 at 10:22:46AM +0530, Sachin Kamat wrote:
>> Hi Joonyoung,
>>
>> On Thu, Jul 10, 2014 at 9:53 AM, Joonyoung Shim <jy0922.shim@samsung.com> wrote:
>>> This fixes below build warning.
>>>
>>> drivers/usb/misc/usb3503.c: In function ‘usb3503_probe’:
>>> drivers/usb/misc/usb3503.c:195:11: warning: ‘err’ may be used uninitialized in this function [-Wmaybe-uninitialized]
>>>     dev_err(dev, "unable to request refclk (%d)\n", err);
>>>            ^
>>
>> This has been fixed and availabe in Greg's usb-next tree.
>> https://git.kernel.org/cgit/linux/kernel/git/gregkh/usb.git/commit/?h=usb-next&id=ec5734c41bee2ee7c938a8f34853d31cada7e67a
> 
> Yes, Joonyoung, can you refresh this against my latest tree and resend
> anything that is still needed in this series?
> 

Aha, i missed it, ok i will resend.

Thanks.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/