[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180712063506.GA25007@kroah.com>
Date: Thu, 12 Jul 2018 08:35:06 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Pawel Laszczak <pawell@...ence.com>
Cc: "linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
Felipe Balbi <balbi@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Lukasz Tyrala <ltyrala@...ence.com>,
Alan Douglas <adouglas@...ence.com>
Subject: Re: [PATCH 02/31] usb: usbssp: Added some decoding functions.
On Thu, Jul 12, 2018 at 06:28:33AM +0000, Pawel Laszczak wrote:
> > > This patch add additional functions that converts some fields to string.
> > >
> > > For example function usbssp_trb_comp_code_string take completion c ode
> > > value and return string describing completion code.
> >
> > Odd line-wrapping :(
> Do you mean additional space character between "c" and "ode"
It wrapped lines at that point for me, yes.
> > And why do you want a string for these things? Who cares about them?
> It will be used in next version of driver. I have plan to add gadget-debugfs.c file.
> At this moment this functions can be useful during debugging driver if someone want to display
> some debug information.
>
> Should I remove this function ?
If no one is using it now, yes, it does not need to be there, right? We
don't have dead code around for no reason, otherwise someone will come
along and remove it :)
thanks,
greg k-h
Powered by blists - more mailing lists