From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
To: Aliasgar Surti <aliasgar.surti500@gmail.com>,
mchehab@kernel.org, gregkh@linuxfoundation.org,
sakari.ailus@linux.intel.com, linux-media@vger.kernel.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] staging: media: fix style problem
Date: Tue, 25 Jun 2019 09:17:46 +0200 [thread overview]
Message-ID: <6536b57d-fea2-e16d-2092-e9e27c51c0f1@xs4all.nl> (raw)
In-Reply-To: <1561099192-19638-1-git-send-email-aliasgar.surti500@gmail.com>
On 6/21/19 8:39 AM, Aliasgar Surti wrote:
> From: Aliasgar Surti <aliasgar.surti500@gmail.com>
>
> checkpatch reported "WARNING: line over 80 characters".
> This patch fixes the warning for file soc_camera/soc_ov5642.c
FYI: we're not accepting patches for staging/media/soc_camera: these
are obsolete and broken drivers.
Regards,
Hans
>
> Signed-off-by: Aliasgar Surti <aliasgar.surti500@gmail.com>
> ---
> drivers/staging/media/soc_camera/soc_ov5642.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/media/soc_camera/soc_ov5642.c b/drivers/staging/media/soc_camera/soc_ov5642.c
> index 94696d7..39ae24dc 100644
> --- a/drivers/staging/media/soc_camera/soc_ov5642.c
> +++ b/drivers/staging/media/soc_camera/soc_ov5642.c
> @@ -687,7 +687,8 @@ static int reg_write16(struct i2c_client *client, u16 reg, u16 val16)
> }
>
> #ifdef CONFIG_VIDEO_ADV_DEBUG
> -static int ov5642_get_register(struct v4l2_subdev *sd, struct v4l2_dbg_register *reg)
> +static int ov5642_get_register(struct v4l2_subdev *sd,
> + struct v4l2_dbg_register *reg)
> {
> struct i2c_client *client = v4l2_get_subdevdata(sd);
> int ret;
> @@ -705,7 +706,8 @@ static int ov5642_get_register(struct v4l2_subdev *sd, struct v4l2_dbg_register
> return ret;
> }
>
> -static int ov5642_set_register(struct v4l2_subdev *sd, const struct v4l2_dbg_register *reg)
> +static int ov5642_set_register(struct v4l2_subdev *sd,
> + const struct v4l2_dbg_register *reg)
> {
> struct i2c_client *client = v4l2_get_subdevdata(sd);
>
>
next prev parent reply other threads:[~2019-06-25 7:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 6:39 [PATCH 1/1] staging: media: fix style problem Aliasgar Surti
2019-06-25 7:17 ` Hans Verkuil [this message]
2019-06-25 13:22 ` Joe Perches
-- strict thread matches above, loose matches on Subject: below --
2019-06-20 5:31 Aliasgar Surti
2019-06-20 21:25 ` André Almeida
2019-06-20 5:02 Aliasgar Surti
2019-06-20 5:09 ` Nathan Chancellor
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=6536b57d-fea2-e16d-2092-e9e27c51c0f1@xs4all.nl \
--to=hverkuil-cisco@xs4all.nl \
--cc=aliasgar.surti500@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=sakari.ailus@linux.intel.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;
as well as URLs for NNTP newsgroup(s).