Re: [PATCH V2] usb: dwc2: host: fix Wmaybe-uninitialized warning

2017-01-12 Thread John Youn
On 1/12/2017 8:32 AM, Nicholas Mc Guire wrote: > Uninitialized char* causes a sparse build-warning, fix it up by > initializing it to NULL. > > Signed-off-by: Nicholas Mc Guire > --- > > V2: add missing change-log as requested by Greg Kroah-Hartman >

Re: [PATCH V2] usb: dwc2: host: fix Wmaybe-uninitialized warning

2017-01-12 Thread John Youn
On 1/12/2017 8:32 AM, Nicholas Mc Guire wrote: > Uninitialized char* causes a sparse build-warning, fix it up by > initializing it to NULL. > > Signed-off-by: Nicholas Mc Guire > --- > > V2: add missing change-log as requested by Greg Kroah-Hartman > > > Problem reported by sparse >

[PATCH V2] usb: dwc2: host: fix Wmaybe-uninitialized warning

2017-01-12 Thread Nicholas Mc Guire
Uninitialized char* causes a sparse build-warning, fix it up by initializing it to NULL. Signed-off-by: Nicholas Mc Guire --- V2: add missing change-log as requested by Greg Kroah-Hartman Problem reported by sparse drivers/usb/dwc2/hcd.c: In

[PATCH V2] usb: dwc2: host: fix Wmaybe-uninitialized warning

2017-01-12 Thread Nicholas Mc Guire
Uninitialized char* causes a sparse build-warning, fix it up by initializing it to NULL. Signed-off-by: Nicholas Mc Guire --- V2: add missing change-log as requested by Greg Kroah-Hartman Problem reported by sparse drivers/usb/dwc2/hcd.c: In function 'dwc2_dump_urb_info':