From: Shuah Khan <shuahkh@osg.samsung.com>
To: Krzysztof Opasiak <k.opasiak@samsung.com>,
valentina.manea.m@gmail.com, shuah@kernel.org,
gregkh@linuxfoundation.org
Cc: yuyang.du@intel.com, nobuo.iwata@fujixerox.co.jp,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH] usbip: tools usbip_attach: Fix cryptic error messages
Date: Tue, 27 Feb 2018 15:51:43 -0700 [thread overview]
Message-ID: <86353881-6807-7ca4-960e-2d1f8a428658@osg.samsung.com> (raw)
In-Reply-To: <8b7b3f6a-4075-e7e3-39ac-51ddb8f961a0@samsung.com>
On 02/27/2018 03:45 PM, Krzysztof Opasiak wrote:
>
>
> On 02/27/2018 11:23 PM, Shuah Khan wrote:
>> Attach device error message is cryptic and useless. Fix it to be
>> informative.
>>
>> Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
>> ---
>> tools/usb/usbip/src/usbip_attach.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/tools/usb/usbip/src/usbip_attach.c b/tools/usb/usbip/src/usbip_attach.c
>> index 7f07b2d50f59..f60738735398 100644
>> --- a/tools/usb/usbip/src/usbip_attach.c
>> +++ b/tools/usb/usbip/src/usbip_attach.c
>> @@ -195,7 +195,8 @@ static int attach_device(char *host, char *busid)
>> rhport = query_import_device(sockfd, busid);
>> if (rhport < 0) {
>> - err("query");
>> + err("Attach request for Device %s. Is this device exported?",
>> + busid);
>> return -1;
>> }
>
> The code itself is ok and you may put my:
>
> Reviewed-by: Krzysztof Opasiak <k.opasiak@samsung.com>
>
> but just because of my curiosity, there is a number of places in usbip tools where the same level of descriptiveness is used for error message. Why did you choose to fix this one not any other or all others?;)
>
> Best regards,
Yes there are several very cryptic and useless error message all over the
place in usbip tools that could use refinement. This just happens to be the
one that I seem to run into very frequently. It frustrated me enough that
I decided to fix this one first. :)
thanks,
-- Shuah
prev parent reply other threads:[~2018-02-27 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180227222421epcas2p23e030c5de1620f5976cf4f91a2685682@epcas2p2.samsung.com>
2018-02-27 22:23 ` Shuah Khan
2018-02-27 22:23 ` [PATCH] usbip: tools usbip_network: " Shuah Khan
2018-02-27 22:45 ` [PATCH] usbip: tools usbip_attach: " Krzysztof Opasiak
2018-02-27 22:51 ` Shuah Khan [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=86353881-6807-7ca4-960e-2d1f8a428658@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=k.opasiak@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nobuo.iwata@fujixerox.co.jp \
--cc=shuah@kernel.org \
--cc=valentina.manea.m@gmail.com \
--cc=yuyang.du@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®