[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210106145100.GJ2809@kadam>
Date: Wed, 6 Jan 2021 17:51:00 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Zheng Yongjun <zhengyongjun3@...wei.com>
Cc: clabbe@...libre.com, mchehab@...nel.org,
mjpeg-users@...ts.sourceforge.net, linux-media@...r.kernel.org,
devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
gregkh@...uxfoundation.org
Subject: Re: [PATCH -next] media: zoran: use resource_size
On Wed, Jan 06, 2021 at 09:17:02PM +0800, Zheng Yongjun wrote:
> Use resource_size rather than a verbose computation on
> the end and start fields.
>
> Signed-off-by: Zheng Yongjun <zhengyongjun3@...wei.com>
> ---
> drivers/staging/media/zoran/zoran_driver.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/media/zoran/zoran_driver.c b/drivers/staging/media/zoran/zoran_driver.c
> index 808196ea5b81..d60b4c73ea80 100644
> --- a/drivers/staging/media/zoran/zoran_driver.c
> +++ b/drivers/staging/media/zoran/zoran_driver.c
> @@ -1020,7 +1020,7 @@ int zoran_queue_init(struct zoran *zr, struct vb2_queue *vq)
> vq->buf_struct_size = sizeof(struct zr_buffer);
> vq->ops = &zr_video_qops;
> vq->mem_ops = &vb2_dma_contig_memops;
> - vq->gfp_flags = GFP_DMA32,
> + vq->gfp_flags = GFP_DMA32;
The commit doesn't match the patch. Also this driver is in
staging because it's going to be deleted soon so there probably isn't
much point doing cleanups.
If you're looking at the Smatch resource_size() message, then that's a
tricky thing because of the + 1 on part of the "end - start + 1"...
It's sometimes hard to know if we should add the + 1 which resource_size()
does or not. (That check is ancient and not up to modern standards).
regards,
dan carpenter
Powered by blists - more mailing lists