From: Joonyoung Shim <jy0922.shim@samsung.com>
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
Date: Thu, 10 Jul 2014 14:11:22 +0900 [thread overview]
Message-ID: <53BE207A.8020800@samsung.com> (raw)
In-Reply-To: <20140710050539.GD14064@kroah.com>
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.
prev parent reply other threads:[~2014-07-10 5:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 4:23 [PATCH 1/3] usb: usb3503: fix build warning Joonyoung Shim
2014-07-10 4:23 ` [PATCH 2/3] usb: usb3503: add PM functions Joonyoung Shim
2014-07-10 4:23 ` [PATCH 3/3] USB: add reset resume quirk for usb3503 Joonyoung Shim
2014-07-10 4:52 ` [PATCH 1/3] usb: usb3503: fix build warning Sachin Kamat
2014-07-10 5:05 ` Greg Kroah-Hartman
2014-07-10 5:11 ` Joonyoung Shim [this message]
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=53BE207A.8020800@samsung.com \
--to=jy0922.shim@samsung.com \
--cc=broonie@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=spk.linux@gmail.com \
--cc=tobetter@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.