From: Aliasgar Surti <aliasgar.surti500@gmail.com>
To: linux-media@vger.kernel.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org
Cc: Aliasgar Surti <aliasgar.surti500@gmail.com>
Subject: [PATCH 1/1] staging: media: fix style problem
Date: Thu, 20 Jun 2019 10:32:48 +0530 [thread overview]
Message-ID: <1561006968-29717-1-git-send-email-aliasgar.surti500@gmail.com> (raw)
From: Aliasgar Surti <aliasgar.surti500@gmail.com>
checkpatch reported "WARNING: line over 80 characters".
This patch fixes the warning for file davinci_vpfe/dm365_isif.c
Signed-off-by: Aliasgar Surti <aliasgar.surti500@gmail.com>
---
drivers/staging/media/davinci_vpfe/dm365_isif.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/media/davinci_vpfe/dm365_isif.c b/drivers/staging/media/davinci_vpfe/dm365_isif.c
index 46fd818..12bdf91 100644
--- a/drivers/staging/media/davinci_vpfe/dm365_isif.c
+++ b/drivers/staging/media/davinci_vpfe/dm365_isif.c
@@ -532,7 +532,8 @@ static int isif_validate_dfc_params(const struct vpfe_isif_dfc *dfc)
#define DM365_ISIF_MAX_CLVSV 0x1fff
#define DM365_ISIF_MAX_HEIGHT_BLACK_REGION 0x1fff
-static int isif_validate_bclamp_params(const struct vpfe_isif_black_clamp *bclamp)
+static int isif_validate_bclamp_params(const struct vpfe_isif_black_clamp
+ *bclamp)
{
int err = -EINVAL;
@@ -593,7 +594,8 @@ isif_validate_raw_params(const struct vpfe_isif_raw_config *params)
return isif_validate_bclamp_params(¶ms->bclamp);
}
-static int isif_set_params(struct v4l2_subdev *sd, const struct vpfe_isif_raw_config *params)
+static int isif_set_params(struct v4l2_subdev *sd,
+ const struct vpfe_isif_raw_config *params)
{
struct vpfe_isif_device *isif = v4l2_get_subdevdata(sd);
int ret = -EINVAL;
--
2.7.4
next reply other threads:[~2019-06-20 5:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 5:02 Aliasgar Surti [this message]
2019-06-20 5:09 ` [PATCH 1/1] staging: media: fix style problem Nathan Chancellor
2019-06-20 5:31 Aliasgar Surti
2019-06-20 21:25 ` André Almeida
2019-06-21 6:39 Aliasgar Surti
2019-06-25 7:17 ` Hans Verkuil
2019-06-25 13:22 ` Joe Perches
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=1561006968-29717-1-git-send-email-aliasgar.surti500@gmail.com \
--to=aliasgar.surti500@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@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;
as well as URLs for NNTP newsgroup(s).