From: Paul Cercueil <paul@crapouillou.net>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: balbi@kernel.org, gregkh@linuxfoundation.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] usb: phy: jz4770: Add a missing '\n' in a log message
Date: Sat, 11 Apr 2020 15:13:47 +0200 [thread overview]
Message-ID: <ZQKM8Q.561QQF8CXZTU3@crapouillou.net> (raw)
In-Reply-To: <20200411063811.6767-1-christophe.jaillet@wanadoo.fr>
Hi Christophe,
Le sam. 11 avril 2020 à 8:38, Christophe JAILLET
<christophe.jaillet@wanadoo.fr> a écrit :
> Message logged by 'dev_xxx()' or 'pr_xxx()' should end with a '\n'.
Is that so?
From what I could see these macros add the \n themselves if needed. So
the \n were omitted on purpose.
-Paul
> Fixes: 541368b46b82 ("usb: phy: Add driver for the Ingenic JZ4770 USB
> transceiver")
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> drivers/usb/phy/phy-jz4770.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/usb/phy/phy-jz4770.c
> b/drivers/usb/phy/phy-jz4770.c
> index 3ea1f5b9bcf8..8f62dc2a90ff 100644
> --- a/drivers/usb/phy/phy-jz4770.c
> +++ b/drivers/usb/phy/phy-jz4770.c
> @@ -125,13 +125,13 @@ static int jz4770_phy_init(struct usb_phy *phy)
>
> err = regulator_enable(priv->vcc_supply);
> if (err) {
> - dev_err(priv->dev, "Unable to enable VCC: %d", err);
> + dev_err(priv->dev, "Unable to enable VCC: %d\n", err);
> return err;
> }
>
> err = clk_prepare_enable(priv->clk);
> if (err) {
> - dev_err(priv->dev, "Unable to start clock: %d", err);
> + dev_err(priv->dev, "Unable to start clock: %d\n", err);
> return err;
> }
>
> @@ -191,7 +191,7 @@ static int jz4770_phy_probe(struct
> platform_device *pdev)
>
> priv->base = devm_platform_ioremap_resource(pdev, 0);
> if (IS_ERR(priv->base)) {
> - dev_err(dev, "Failed to map registers");
> + dev_err(dev, "Failed to map registers\n");
> return PTR_ERR(priv->base);
> }
>
> @@ -199,7 +199,7 @@ static int jz4770_phy_probe(struct
> platform_device *pdev)
> if (IS_ERR(priv->clk)) {
> err = PTR_ERR(priv->clk);
> if (err != -EPROBE_DEFER)
> - dev_err(dev, "Failed to get clock");
> + dev_err(dev, "Failed to get clock\n");
> return err;
> }
>
> @@ -207,14 +207,14 @@ static int jz4770_phy_probe(struct
> platform_device *pdev)
> if (IS_ERR(priv->vcc_supply)) {
> err = PTR_ERR(priv->vcc_supply);
> if (err != -EPROBE_DEFER)
> - dev_err(dev, "failed to get regulator");
> + dev_err(dev, "Failed to get regulator\n");
> return err;
> }
>
> err = usb_add_phy(&priv->phy, USB_PHY_TYPE_USB2);
> if (err) {
> if (err != -EPROBE_DEFER)
> - dev_err(dev, "Unable to register PHY");
> + dev_err(dev, "Unable to register PHY\n");
> return err;
> }
>
> --
> 2.20.1
>
next prev parent reply other threads:[~2020-04-11 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 6:38 Christophe JAILLET
2020-04-11 13:13 ` Paul Cercueil [this message]
2020-04-11 15:46 ` Joe Perches
2020-04-14 9:31 ` Dan Carpenter
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=ZQKM8Q.561QQF8CXZTU3@crapouillou.net \
--to=paul@crapouillou.net \
--cc=balbi@kernel.org \
--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®