From: Steve Longerbeam <slongerbeam@gmail.com>
To: Parthiban Nallathambi <pn@denx.de>
Cc: devel@driverdev.osuosl.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, p.zabel@pengutronix.de,
mchehab@kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH] staging: media: reformat line to 80 chars or less
Date: Wed, 14 Feb 2018 15:01:52 -0800 [thread overview]
Message-ID: <ee47261e-aa6d-150f-e7f0-b80c74fdec1d@gmail.com> (raw)
In-Reply-To: <20180212120548.7391-1-pn@denx.de>
Hi Parthiban, please rename the commit title to
"media: imx: capture: reformat line to 80 chars or less"
Otherwise it is fine with me.
Steve
On 02/12/2018 04:05 AM, Parthiban Nallathambi wrote:
> This is a cleanup patch to fix line length issue found
> by checkpatch.pl script.
>
> In this patch, line 144 have been wrapped.
>
> Signed-off-by: Parthiban Nallathambi <pn@denx.de>
> ---
> drivers/staging/media/imx/imx-media-capture.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/staging/media/imx/imx-media-capture.c b/drivers/staging/media/imx/imx-media-capture.c
> index 576bdc7e9c42..0ccabe04b0e1 100644
> --- a/drivers/staging/media/imx/imx-media-capture.c
> +++ b/drivers/staging/media/imx/imx-media-capture.c
> @@ -141,7 +141,8 @@ static int capture_enum_frameintervals(struct file *file, void *fh,
>
> fie.code = cc->codes[0];
>
> - ret = v4l2_subdev_call(priv->src_sd, pad, enum_frame_interval, NULL, &fie);
> + ret = v4l2_subdev_call(priv->src_sd, pad, enum_frame_interval,
> + NULL, &fie);
> if (ret)
> return ret;
>
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2018-02-14 23:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 12:05 Parthiban Nallathambi
2018-02-14 23:01 ` Steve Longerbeam [this message]
2018-02-15 9:25 ` [PATCH v2] media: imx: capture: " Parthiban Nallathambi
2018-02-15 17:37 ` Steve Longerbeam
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=ee47261e-aa6d-150f-e7f0-b80c74fdec1d@gmail.com \
--to=slongerbeam@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=pn@denx.de \
/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
Powered by JetHome