mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: "Jackson.lee" <jackson.lee@chipsnmedia.com>,
	mchehab@kernel.org,  hverkuil-cisco@xs4all.nl,
	bob.beckett@collabora.com
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	 lafley.kim@chipsnmedia.com, b-brnich@ti.com, hverkuil@xs4all.nl,
	 nas.chung@chipsnmedia.com
Subject: Re: [PATCH v3 3/4] media: chips-media: wave5: Add WARN_ON to check if dec_output_info is NULL
Date: Fri, 29 Aug 2025 14:15:40 -0400	[thread overview]
Message-ID: <88fc40c386f2609584df72cf4951972b07f20e72.camel@collabora.com> (raw)
In-Reply-To: <20250623002153.51-4-jackson.lee@chipsnmedia.com>

[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]

Le lundi 23 juin 2025 à 09:21 +0900, Jackson.lee a écrit :
> From: Jackson Lee <jackson.lee@chipsnmedia.com>
> 
> The dec_output_info could be a null pointer, so WARN_ON around it
> was added.

I think to warrant a WARN_ON, its should be that the info should NOT be null.
WARN_ON should be used for driver programming issues. If this is what you mean,
I would reword:


   The dec_output_info should not be a null pointer, WARN_ON around it to
   indicates a driver issue.


cheers,
Nicolas

> 
> Signed-off-by: Jackson Lee <jackson.lee@chipsnmedia.com>
> Signed-off-by: Nas Chung <nas.chung@chipsnmedia.com>
> ---
>  drivers/media/platform/chips-media/wave5/wave5-vpuapi.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/media/platform/chips-media/wave5/wave5-vpuapi.c b/drivers/media/platform/chips-media/wave5/wave5-vpuapi.c
> index e94d6ebc9f81..5b10f9f49b9f 100644
> --- a/drivers/media/platform/chips-media/wave5/wave5-vpuapi.c
> +++ b/drivers/media/platform/chips-media/wave5/wave5-vpuapi.c
> @@ -485,7 +485,7 @@ int wave5_vpu_dec_get_output_info(struct vpu_instance *inst, struct dec_output_i
>  	struct vpu_device *vpu_dev = inst->dev;
>  	struct dec_output_info *disp_info;
>  
> -	if (!info)
> +	if (WARN_ON(!info))
>  		return -EINVAL;
>  
>  	p_dec_info = &inst->codec_info->dec_info;

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-08-29 18:15 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-23  0:21 [PATCH v3 0/4] Performance improvement of decoder Jackson.lee
2025-06-23  0:21 ` [PATCH v3 1/4] media: chips-media: wave5: Fix SError of kernel panic when closed Jackson.lee
2025-08-29 18:03   ` Nicolas Dufresne
2025-06-23  0:21 ` [PATCH v3 2/4] media: chips-media: wave5: Fix Null reference while testing fluster Jackson.lee
2025-08-29 18:13   ` Nicolas Dufresne
2025-09-09  3:43     ` jackson.lee
2025-06-23  0:21 ` [PATCH v3 3/4] media: chips-media: wave5: Add WARN_ON to check if dec_output_info is NULL Jackson.lee
2025-08-29 18:15   ` Nicolas Dufresne [this message]
2025-09-09  3:45     ` jackson.lee
2025-06-23  0:21 ` [PATCH v3 4/4] media: chips-media: wave5: Improve performance of decoder Jackson.lee
2025-08-29 18:01   ` Nicolas Dufresne
2025-09-09  1:42     ` jackson.lee
2025-09-16 11:21   ` Markus Elfring
2025-07-07  0:37 ` [PATCH v3 0/4] Performance improvement " jackson.lee
2025-08-12  7:51   ` jackson.lee
2025-08-29 15:40 ` Nicolas Dufresne
2025-09-09  6:16   ` jackson.lee
2025-09-09 21:33     ` Nicolas Dufresne
2025-09-10  6:59       ` jackson.lee
2025-09-10 12:56         ` Nicolas Dufresne
2025-09-11  2:04           ` jackson.lee
2025-09-11 12:23             ` Nicolas Dufresne
2025-09-11  4:40           ` jackson.lee
2025-09-15  7:33           ` jackson.lee
2025-09-15 20:14             ` Nicolas Dufresne
2025-09-16  0:40               ` jackson.lee

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=88fc40c386f2609584df72cf4951972b07f20e72.camel@collabora.com \
    --to=nicolas.dufresne@collabora.com \
    --cc=b-brnich@ti.com \
    --cc=bob.beckett@collabora.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=hverkuil@xs4all.nl \
    --cc=jackson.lee@chipsnmedia.com \
    --cc=lafley.kim@chipsnmedia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nas.chung@chipsnmedia.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

all inboxes | Powered by JetHome®