From: shuah <shuah@kernel.org>
To: Mao Wenan <maowenan@huawei.com>,
valentina.manea.m@gmail.com, gregkh@linuxfoundation.org
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org, shuah <shuah@kernel.org>
Subject: Re: [PATCH v3] usbip: vhci_hcd indicate failed message
Date: Mon, 16 Sep 2019 15:47:21 +0000 [thread overview]
Message-ID: <fb06edbf-e599-ada5-916d-405382cb6f6f@kernel.org> (raw)
In-Reply-To: <20190916150921.152977-1-maowenan@huawei.com>
On 9/16/19 9:09 AM, Mao Wenan wrote:
> If the return value of vhci_init_attr_group and
> sysfs_create_group is non-zero, which mean they failed
> to init attr_group and create sysfs group, so it would
> better add 'failed' message to indicate that.
> This patch also change pr_err to dev_err to trace which
> device is failed.
>
> Fixes: 0775a9cbc694 ("usbip: vhci extension: modifications to vhci driver")
> Signed-off-by: Mao Wenan <maowenan@huawei.com>
> ---
> v2: change pr_err to dev_err.
> v3: add error code in failed messages.
> drivers/usb/usbip/vhci_hcd.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/usbip/vhci_hcd.c b/drivers/usb/usbip/vhci_hcd.c
> index 000ab7225717..144507751eae 100644
> --- a/drivers/usb/usbip/vhci_hcd.c
> +++ b/drivers/usb/usbip/vhci_hcd.c
> @@ -1185,12 +1185,12 @@ static int vhci_start(struct usb_hcd *hcd)
> if (id = 0 && usb_hcd_is_primary_hcd(hcd)) {
> err = vhci_init_attr_group();
> if (err) {
> - pr_err("init attr group\n");
> + dev_err(hcd_dev(hcd), "init attr group failed, err = %d\n", err);
> return err;
> }
> err = sysfs_create_group(&hcd_dev(hcd)->kobj, &vhci_attr_group);
> if (err) {
> - pr_err("create sysfs files\n");
> + dev_err(hcd_dev(hcd), "create sysfs files failed, err = %d\n", err);
> vhci_finish_attr_group();
> return err;
> }
>
Looks good to me.
Acked-by: Shuah Khan <skhan@linuxfoundation.org>
thanks,
-- Shuah
WARNING: multiple messages have this Message-ID (diff)
From: shuah <shuah@kernel.org>
To: Mao Wenan <maowenan@huawei.com>,
valentina.manea.m@gmail.com, gregkh@linuxfoundation.org
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org, shuah <shuah@kernel.org>
Subject: Re: [PATCH v3] usbip: vhci_hcd indicate failed message
Date: Mon, 16 Sep 2019 09:47:21 -0600 [thread overview]
Message-ID: <fb06edbf-e599-ada5-916d-405382cb6f6f@kernel.org> (raw)
In-Reply-To: <20190916150921.152977-1-maowenan@huawei.com>
On 9/16/19 9:09 AM, Mao Wenan wrote:
> If the return value of vhci_init_attr_group and
> sysfs_create_group is non-zero, which mean they failed
> to init attr_group and create sysfs group, so it would
> better add 'failed' message to indicate that.
> This patch also change pr_err to dev_err to trace which
> device is failed.
>
> Fixes: 0775a9cbc694 ("usbip: vhci extension: modifications to vhci driver")
> Signed-off-by: Mao Wenan <maowenan@huawei.com>
> ---
> v2: change pr_err to dev_err.
> v3: add error code in failed messages.
> drivers/usb/usbip/vhci_hcd.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/usbip/vhci_hcd.c b/drivers/usb/usbip/vhci_hcd.c
> index 000ab7225717..144507751eae 100644
> --- a/drivers/usb/usbip/vhci_hcd.c
> +++ b/drivers/usb/usbip/vhci_hcd.c
> @@ -1185,12 +1185,12 @@ static int vhci_start(struct usb_hcd *hcd)
> if (id == 0 && usb_hcd_is_primary_hcd(hcd)) {
> err = vhci_init_attr_group();
> if (err) {
> - pr_err("init attr group\n");
> + dev_err(hcd_dev(hcd), "init attr group failed, err = %d\n", err);
> return err;
> }
> err = sysfs_create_group(&hcd_dev(hcd)->kobj, &vhci_attr_group);
> if (err) {
> - pr_err("create sysfs files\n");
> + dev_err(hcd_dev(hcd), "create sysfs files failed, err = %d\n", err);
> vhci_finish_attr_group();
> return err;
> }
>
Looks good to me.
Acked-by: Shuah Khan <skhan@linuxfoundation.org>
thanks,
-- Shuah
next prev parent reply other threads:[~2019-09-16 15:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-15 3:43 [PATCH] usbip: vhci_hcd indicate failed message Mao Wenan
2019-09-15 3:43 ` Mao Wenan
2019-09-15 12:52 ` Greg KH
2019-09-15 12:52 ` Greg KH
2019-09-15 13:31 ` walter harms
2019-09-15 13:31 ` walter harms
2019-09-15 14:22 ` [PATCH v2] " Mao Wenan
2019-09-15 14:22 ` Mao Wenan
2019-09-16 13:18 ` shuah
2019-09-16 13:18 ` shuah
2019-09-16 14:52 ` [PATCH v3] " Mao Wenan
2019-09-16 15:09 ` Mao Wenan
2019-09-16 15:47 ` shuah [this message]
2019-09-16 15:47 ` shuah
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=fb06edbf-e599-ada5-916d-405382cb6f6f@kernel.org \
--to=shuah@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=maowenan@huawei.com \
--cc=valentina.manea.m@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.