From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Cc: linux-media@vger.kernel.org, Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [PATCH] videobuf2-v4l2: Fix return with value warnings
Date: Sun, 10 Jan 2016 18:23:55 +0200 [thread overview]
Message-ID: <8497172.cxLeiKAFLn@avalon> (raw)
In-Reply-To: <1452441551-19426-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
On Sunday 10 January 2016 17:59:11 Laurent Pinchart wrote:
> Commit 10cc3b1e1296 ("videobuf2-core: fill_user_buffer and
> copy_timestamp should return void") forgot one return statement from the
> videobuf2-v4l2 implementations of copy_timestamp and fill_user_buffer.
> Remove them.
>
> Fixes: 10cc3b1e1296 ("videobuf2-core: fill_user_buffer and copy_timestamp
> should return void")
And that commit isn't upstream -_-'
Sorry for the noise.
> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> ---
> drivers/media/v4l2-core/videobuf2-v4l2.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/media/v4l2-core/videobuf2-v4l2.c
> b/drivers/media/v4l2-core/videobuf2-v4l2.c index a15cd1b4c7f0..bbbd8e1b1a99
> 100644
> --- a/drivers/media/v4l2-core/videobuf2-v4l2.c
> +++ b/drivers/media/v4l2-core/videobuf2-v4l2.c
> @@ -121,7 +121,7 @@ static void __copy_timestamp(struct vb2_buffer *vb,
> const void *pb) struct vb2_queue *q = vb->vb2_queue;
>
> if (!pb)
> - return 0;
> + return;
>
> if (q->is_output) {
> /*
> @@ -197,7 +197,7 @@ static void __fill_v4l2_buffer(struct vb2_buffer *vb,
> void *pb) unsigned int plane;
>
> if (!pb)
> - return 0;
> + return;
>
> /* Copy back data such as timestamp, flags, etc. */
> b->index = vb->index;
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2016-01-10 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-10 15:59 [PATCH] videobuf2-v4l2: Fix return with value warnings Laurent Pinchart
2016-01-10 16:23 ` Laurent Pinchart [this message]
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=8497172.cxLeiKAFLn@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=hans.verkuil@cisco.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.