From: Chunfeng Yun <chunfeng.yun@mediatek.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: <linux-kernel@vger.kernel.org>, <kernel-janitors@vger.kernel.org>,
<linux-usb@vger.kernel.org>
Subject: Re: [PATCH] usb: common: usb-conn-gpio: Simplify some error message
Date: Mon, 8 Aug 2022 16:35:11 +0800 [thread overview]
Message-ID: <63920b2ae09e8f82a9b866cd01ddb63b958fb4e8.camel@mediatek.com> (raw)
In-Reply-To: <7705a9dff8e097070c492d6f4f8aafaaa890f049.1659763173.git.christophe.jaillet@wanadoo.fr>
On Sat, 2022-08-06 at 07:19 +0200, Christophe JAILLET wrote:
> dev_err_probe() already prints the error code in a human readable
> way, so
> there is no need to duplicate it as a numerical value at the end of
> the
> message.
>
> Fixes: ddaf0d6dc467 ("usb: common: usb-conn-gpio: use dev_err_probe()
> to print log")
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> drivers/usb/common/usb-conn-gpio.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/usb/common/usb-conn-gpio.c
> b/drivers/usb/common/usb-conn-gpio.c
> index b39c9f1c375d..44c5127175b7 100644
> --- a/drivers/usb/common/usb-conn-gpio.c
> +++ b/drivers/usb/common/usb-conn-gpio.c
> @@ -208,10 +208,9 @@ static int usb_conn_probe(struct platform_device
> *pdev)
> if (PTR_ERR(info->vbus) == -ENODEV)
> info->vbus = NULL;
>
> - if (IS_ERR(info->vbus)) {
> - ret = PTR_ERR(info->vbus);
> - return dev_err_probe(dev, ret, "failed to get vbus
> :%d\n", ret);
> - }
> + if (IS_ERR(info->vbus))
> + return dev_err_probe(dev, PTR_ERR(info->vbus),
> + "failed to get vbus\n");
How about putting dev_err_probe() in a single line? it doesn't exceed
100 chars.
>
> info->role_sw = usb_role_switch_get(dev);
> if (IS_ERR(info->role_sw))
prev parent reply other threads:[~2022-08-08 8:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 5:19 Christophe JAILLET
2022-08-08 8:35 ` Chunfeng Yun [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=63920b2ae09e8f82a9b866cd01ddb63b958fb4e8.camel@mediatek.com \
--to=chunfeng.yun@mediatek.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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®