From: Sean Young <sean@mess.org>
To: Dongliang Mu <mudongliangabcd@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3 v2] media: dvb-usb: break long strings in dvb_usb_device_init
Date: Tue, 13 Jul 2021 09:52:59 +0100 [thread overview]
Message-ID: <20210713085259.GB6572@gofer.mess.org> (raw)
In-Reply-To: <20210621113959.53320-1-mudongliangabcd@gmail.com>
On Mon, Jun 21, 2021 at 07:39:59PM +0800, Dongliang Mu wrote:
> Break long strings into multiple lines.
>
> Signed-off-by: Dongliang Mu <mudongliangabcd@gmail.com>
> ---
> drivers/media/usb/dvb-usb/dvb-usb-init.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/media/usb/dvb-usb/dvb-usb-init.c b/drivers/media/usb/dvb-usb/dvb-usb-init.c
> index 28e1fd64dd3c..edc477cedaa9 100644
> --- a/drivers/media/usb/dvb-usb/dvb-usb-init.c
> +++ b/drivers/media/usb/dvb-usb/dvb-usb-init.c
> @@ -286,13 +286,15 @@ int dvb_usb_device_init(struct usb_interface *intf,
>
> desc = dvb_usb_find_device(udev, &d->props, &cold);
> if (!desc) {
> - deb_err("something went very wrong, device was not found in current device list - let's see what comes next.\n");
> + deb_err("something went very wrong, "
> + "device was not found in current device list.\n");
Long lines are acceptable unto 100 columns or more if they are string
constants. Breaking them up does not increase readability.
> ret = -ENODEV;
> goto error;
> }
>
> if (cold) {
> - info("found a '%s' in cold state, will try to load a firmware", desc->name);
> + info("found a %s in cold state, will try to load a firmware",
> + desc->name);
No reason for removing the quotes, I think.
> ret = dvb_usb_download_firmware(udev, props);
> if (!props->no_reconnect || ret != 0)
> goto error;
> @@ -314,7 +316,7 @@ int dvb_usb_device_init(struct usb_interface *intf,
> if (du)
> *du = d;
>
> - info("%s successfully initialized and connected.", desc->name);
> + info("%s is successfully initialized and connected.", desc->name);
"is" doesn't really add anything here, and the message is fine without it.
> return 0;
>
> error:
> --
> 2.25.1
next prev parent reply other threads:[~2021-07-13 8:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 11:39 Dongliang Mu
2021-07-13 8:52 ` Sean Young [this message]
2021-07-13 13:14 ` Dongliang Mu
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=20210713085259.GB6572@gofer.mess.org \
--to=sean@mess.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mudongliangabcd@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 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®