From: Dan Carpenter <dan.carpenter@linaro.org>
To: "Colin King (gmail)" <colin.i.king@gmail.com>
Cc: Yong Zhi <yong.zhi@intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Bingbu Cao <bingbu.cao@intel.com>,
Tianshu Qiu <tian.shu.qiu@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"mailing list: linux-media" <linux-media@vger.kernel.org>,
"linux-staging@lists.linux.dev" <linux-staging@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: media: staging/intel-ipu3: css - possible typo in array being assigned
Date: Fri, 8 Aug 2025 17:17:52 +0300 [thread overview]
Message-ID: <aJYHECY1gjZ2xsSP@stanley.mountain> (raw)
In-Reply-To: <9b3313da-9cc3-4d3e-b271-05ee36736e4f@gmail.com>
Yeah... It probably should be the below patch. The commit message would
say something like:
Subject: Fix copy and paste bug.
This code is copy and pasted from earlier in the function and the NULL
check should be if (p_pl) instead of if (p_tr). Except that p_pl is
never NULL and the check can be removed.
The impact of this bug is that for several callers the
"p_pl[pl_idx].cfg_set = pl_cfg_set" value is never set. (I wonder why
this didn't show up in testing?)"
regards,
dan carpenter
diff --git a/drivers/staging/media/ipu3/ipu3-css-params.c b/drivers/staging/media/ipu3/ipu3-css-params.c
index 2c48d57a3180..2d1c38119258 100644
--- a/drivers/staging/media/ipu3/ipu3-css-params.c
+++ b/drivers/staging/media/ipu3/ipu3-css-params.c
@@ -1617,10 +1617,9 @@ imgu_css_acc_process_lines(const struct process_lines *pl,
/* Inside the grid */
p_pl[pl_idx].lines = process_lines;
- if (p_tr) {
- p_pl[pl_idx].cfg_set = pl_cfg_set;
- pl_cfg_set = 1 - pl_cfg_set;
- }
+ p_pl[pl_idx].cfg_set = pl_cfg_set;
+ pl_cfg_set = 1 - pl_cfg_set;
+
pl_idx++;
}
}
prev parent reply other threads:[~2025-08-08 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 10:06 media: staging/intel-ipu3: css - possible typo in array being assigned Colin King (gmail)
2025-08-08 14:17 ` Dan Carpenter [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=aJYHECY1gjZ2xsSP@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=bingbu.cao@intel.com \
--cc=colin.i.king@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tian.shu.qiu@intel.com \
--cc=yong.zhi@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).