From: Ozgur Karatas <okaratas@member.fsf.org>
To: Avraham Shukron <avraham.shukron@gmail.com>,
"laurent.pinchart@ideasonboard.com"
<laurent.pinchart@ideasonboard.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Staging: omap4iss: fix coding style issues
Date: Sun, 29 Jan 2017 09:31:57 +0200 [thread overview]
Message-ID: <6973561485675117@web6h.yandex.ru> (raw)
In-Reply-To: <1485626408-9768-1-git-send-email-avraham.shukron@gmail.com>
28.01.2017, 20:11, "Avraham Shukron" <avraham.shukron@gmail.com>:
> This is a patch that fixes issues in omap4iss/iss_video.c
> Specifically, it fixes "line over 80 characters" issues
Hello,
are you have a sent this changes patch before?
And Greg KH answered you, are you read?
Please send the change once, there is no need for a repeat.
> Signed-off-by: Avraham Shukron <avraham.shukron@gmail.com>
>
> ---
> drivers/staging/media/omap4iss/iss_video.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/media/omap4iss/iss_video.c b/drivers/staging/media/omap4iss/iss_video.c
> index c16927a..cdab053 100644
> --- a/drivers/staging/media/omap4iss/iss_video.c
> +++ b/drivers/staging/media/omap4iss/iss_video.c
> @@ -298,7 +298,8 @@ iss_video_check_format(struct iss_video *video, struct iss_video_fh *vfh)
>
> static int iss_video_queue_setup(struct vb2_queue *vq,
> unsigned int *count, unsigned int *num_planes,
> - unsigned int sizes[], struct device *alloc_devs[])
> + unsigned int sizes[],
> + struct device *alloc_devs[])
it should be on the same line, maintainer's up to 80 characters allowed.
this "alloc_devs" variable start with int?
Example:
struct device {
int (struct device *alloc_devs[);
Check the top lines of the codes.
> {
> struct iss_video_fh *vfh = vb2_get_drv_priv(vq);
> struct iss_video *video = vfh->video;
> @@ -678,8 +679,8 @@ iss_video_get_selection(struct file *file, void *fh, struct v4l2_selection *sel)
> if (subdev == NULL)
> return -EINVAL;
>
> - /* Try the get selection operation first and fallback to get format if not
> - * implemented.
> + /* Try the get selection operation first and fallback to get format if
> + * not implemented.
> */
There is no change here, it opens with comment /* and closes with */.
Please read submittting patch document.
Regards,
> sdsel.pad = pad;
> ret = v4l2_subdev_call(subdev, pad, get_selection, NULL, &sdsel);
> --
> 2.7.4
~Ozgur
next prev parent reply other threads:[~2017-01-29 7:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-28 18:00 [PATCH] Staging: omap4iss: fix coding style issues Avraham Shukron
2017-01-29 7:31 ` Ozgur Karatas [this message]
2017-01-29 22:42 ` Avraham Shukron
2017-01-30 17:47 ` Laurent Pinchart
2017-01-31 10:42 ` Sakari Ailus
2017-01-31 10:46 ` Laurent Pinchart
2017-02-06 17:58 ` [PATCH v2] Staging: omap4iss: Fix " Avraham Shukron
2017-02-07 8:12 ` Greg KH
2017-02-07 15:40 ` [PATCH v3 1/2] staging: omap4iss: fix multiline comment style Avraham Shukron
2017-02-07 15:40 ` [PATCH v3 2/2] staging: omap4iss: fix coding style issue Avraham Shukron
2017-02-09 11:06 ` [PATCH v3 1/2] staging: omap4iss: fix multiline comment style Greg KH
2017-02-09 16:57 ` [PATCH v4 " Avraham Shukron
2017-02-09 17:01 ` [PATCH v4 2/2] staging: omap4iss: fix coding style issue Avraham Shukron
2017-02-10 7:48 ` [PATCH v4 1/2] staging: omap4iss: fix multiline comment style Laurent Pinchart
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=6973561485675117@web6h.yandex.ru \
--to=okaratas@member.fsf.org \
--cc=avraham.shukron@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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