From: "sakari.ailus@linux.intel.com" <sakari.ailus@linux.intel.com>
To: Bin Du <Bin.Du@amd.com>
Cc: "Limonciello, Mario" <Mario.Limonciello@amd.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"hverkuil@xs4all.nl" <hverkuil@xs4all.nl>,
"laurent.pinchart+renesas@ideasonboard.com"
<laurent.pinchart+renesas@ideasonboard.com>,
"bryan.odonoghue@linaro.org" <bryan.odonoghue@linaro.org>,
"prabhakar.mahadev-lad.rj@bp.renesas.com"
<prabhakar.mahadev-lad.rj@bp.renesas.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"sultan@kerneltoast.com" <sultan@kerneltoast.com>,
"Nirujogi, Pratap" <Pratap.Nirujogi@amd.com>,
"Chan, Benjamin (Koon Pan)" <Benjamin.Chan@amd.com>,
"Li, King" <King.Li@amd.com>,
"gjorgji.rosikopulos@amd.com" <gjorgji.rosikopulos@amd.com>,
"Jawich, Phil" <Phil.Jawich@amd.com>,
"Antony, Dominic" <Dominic.Antony@amd.com>,
"Gong, Richard" <Richard.Gong@amd.com>,
"Tsao, Anson" <anson.tsao@amd.com>
Subject: Re: [PATCH v10 0/7] Add AMD ISP4 driver
Date: Thu, 7 May 2026 12:34:02 +0300 [thread overview]
Message-ID: <afxcirtLHxeiaqF7@kekkonen.localdomain> (raw)
In-Reply-To: <f68addf9-eb16-4c87-b281-b4f1dcc4cc63@amd.com>
Hi Bin,
On Thu, May 07, 2026 at 02:44:32PM +0800, Bin Du wrote:
> Hi Sakari,
>
> I'm not sure which Smatch version is used in Media CI. Here are some
> findings from my local tests for reference.
>
> For v10, I could reproduce the false positive with an older Smatch snapshot
> built from upstream commit URL:https://repo.or.cz/smatch.git/commit/bc575c7a0c5c7a2d4fefd0e1d8b0dc9ccacdd1a6,
> which is a pre-1.74 snapshot.
>
> I could not reproduce the same false positive with a newer Smatch snapshot
> based on upstream commit URL:https://repo.or.cz/smatch.git/commit/bcc58b9ccf06d28ab6be4f0992bc74f462aa12f8,
> which is a post-1.75 snapshot.
>
> For v11, neither Smatch snapshot reports the warning.
That's nice. Smatch is updated weekly so we should get the new smatch in
soon and you could post a patch to remove the workaround. The code would be
nicer without that.
The patches themselves were merged earlier today to the media committers
tree.
--
Regards,
Sakari Ailus
next prev parent reply other threads:[~2026-05-07 9:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 8:41 [PATCH v10 0/7] Add AMD ISP4 driver Bin Du
2026-03-20 8:41 ` [PATCH v10 1/7] media: platform: amd: Introduce amd isp4 capture driver Bin Du
2026-03-20 8:41 ` [PATCH v10 2/7] media: platform: amd: low level support for isp4 firmware Bin Du
2026-03-20 8:41 ` [PATCH v10 3/7] media: platform: amd: Add isp4 fw and hw interface Bin Du
2026-03-20 8:41 ` [PATCH v10 4/7] media: platform: amd: isp4 subdev and firmware loading handling added Bin Du
2026-03-20 8:41 ` [PATCH v10 5/7] media: platform: amd: isp4 video node and buffers " Bin Du
2026-03-20 8:41 ` [PATCH v10 6/7] media: platform: amd: isp4 debug fs logging and more descriptive errors Bin Du
2026-03-20 8:41 ` [PATCH v10 7/7] Documentation: add documentation of AMD isp 4 driver Bin Du
2026-03-20 10:26 ` [PATCH v10 0/7] Add AMD ISP4 driver Du, Bin
2026-03-20 14:01 ` Mario Limonciello
2026-04-03 3:17 ` Du, Bin
2026-04-07 6:35 ` sakari.ailus
2026-04-07 7:19 ` Bin Du
2026-05-05 20:24 ` sakari.ailus
2026-05-06 9:41 ` Bin Du
2026-05-07 6:44 ` Bin Du
2026-05-07 9:34 ` sakari.ailus [this message]
[not found] ` <bd5ab106-e0ef-47d5-aefa-7304ad84105a@amd.com>
2026-05-08 21:30 ` sakari.ailus
2026-05-09 1:59 ` Bin Du
2026-05-09 23:49 ` Ricardo Ribalda
2026-05-11 7:17 ` Bin Du
[not found] ` <69bd3a57.050a0220.1b4541.789b@mx.google.com>
2026-03-23 3:32 ` [v10,0/7] " Du, Bin
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=afxcirtLHxeiaqF7@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=Benjamin.Chan@amd.com \
--cc=Bin.Du@amd.com \
--cc=Dominic.Antony@amd.com \
--cc=King.Li@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=Phil.Jawich@amd.com \
--cc=Pratap.Nirujogi@amd.com \
--cc=Richard.Gong@amd.com \
--cc=anson.tsao@amd.com \
--cc=bryan.odonoghue@linaro.org \
--cc=gjorgji.rosikopulos@amd.com \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=sultan@kerneltoast.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