Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753076AbcJCJfO (ORCPT ); Mon, 3 Oct 2016 05:35:14 -0400 Received: from galahad.ideasonboard.com ([185.26.127.97]:43037 "EHLO galahad.ideasonboard.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752455AbcJCJfE (ORCPT ); Mon, 3 Oct 2016 05:35:04 -0400 From: Laurent Pinchart To: Harman Kalra Cc: mchehab@kernel.org, gregkh@linuxfoundation.org, linux-media@vger.kernel.org, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] [media] : Removing warnings caught by checkpatch.pl Date: Mon, 03 Oct 2016 12:34:58 +0300 Message-ID: <295099868.3eYuVXyQ9F@avalon> User-Agent: KMail/4.14.10 (Linux/4.4.6-gentoo; KDE/4.14.24; x86_64; ; ) In-Reply-To: <1475355646-6378-1-git-send-email-harman4linux@gmail.com> References: <1475355646-6378-1-git-send-email-harman4linux@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2272 Lines: 66 Hello Harman, Thank you for the patch. The subject of your commit message should at least contain the name of the driver. Furthermore, you can mention that the patch originates from warnings output by checkpatch.pl, but the subject should describe what you fix (in this case what type of warning). On Sunday 02 Oct 2016 02:30:45 Harman Kalra wrote: > Removing warnings caught by checkpatch.pl If the purpose of commit message bodies was to repeat the subject line, we wouldn't use them :-) Here you should describe why this change is needed, and possibly how it is performed when the patch is complex (which isn't the case of this patch). > Signed-off-by: Harman Kalra > --- > drivers/staging/media/omap4iss/iss_video.c | 8 ++++---- > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/drivers/staging/media/omap4iss/iss_video.c > b/drivers/staging/media/omap4iss/iss_video.c index c16927a..7cc1691 100644 > --- a/drivers/staging/media/omap4iss/iss_video.c > +++ b/drivers/staging/media/omap4iss/iss_video.c > @@ -297,8 +297,8 @@ static void iss_video_pix_to_mbus(const struct > v4l2_pix_format *pix, */ > > 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 *count, unsigned int *num_planes, > + unsigned int sizes[], struct device *alloc_devs[]) This breaks the coding style of the driver which aligns function arguments to the opening parenthesis. You can instead wrap the last line to shorten it. > { > struct iss_video_fh *vfh = vb2_get_drv_priv(vq); > struct iss_video *video = vfh->video; > @@ -678,8 +678,8 @@ void omap4iss_video_cancel_stream(struct iss_video > *video) 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. Lines can be up to 80 characters long, there's no need to wrap them after 52 characters only. > */ > sdsel.pad = pad; > ret = v4l2_subdev_call(subdev, pad, get_selection, NULL, &sdsel); > -- > 1.7.9.5 -- Regards, Laurent Pinchart