From: Dan Carpenter <dan.carpenter@linaro.org>
To: Dmitry Osipenko <dmitry.osipenko@collabora.com>
Cc: Shreeya Patel <shreeya.patel@collabora.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Dingxian Wen <shawn.wen@rock-chips.com>,
linux-media@vger.kernel.org, kernel@collabora.com,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH next] media: synopsys: hdmirx: Fix signedness bug in hdmirx_parse_dt()
Date: Fri, 7 Mar 2025 12:45:11 +0300 [thread overview]
Message-ID: <4a50949d-e472-4942-9152-3e5a54c6b076@stanley.mountain> (raw)
In-Reply-To: <54d5eef8-66a9-44aa-9e9b-0324d6fee46d@collabora.com>
On Fri, Mar 07, 2025 at 12:36:47PM +0300, Dmitry Osipenko wrote:
> On 3/7/25 12:30, Dan Carpenter wrote:
> > diff --git a/drivers/media/platform/synopsys/hdmirx/snps_hdmirx.c b/drivers/media/platform/synopsys/hdmirx/snps_hdmirx.c
> > index 4ffc86ad6c35..e0d3fed87a92 100644
> > --- a/drivers/media/platform/synopsys/hdmirx/snps_hdmirx.c
> > +++ b/drivers/media/platform/synopsys/hdmirx/snps_hdmirx.c
> > @@ -154,7 +154,7 @@ struct snps_hdmirx_dev {
> > bool hpd_trigger_level_high;
> > bool tmds_clk_ratio;
> > bool plugged;
> > - u32 num_clks;
> > + int num_clks;
> > u32 edid_blocks_written;
> > u32 cur_fmt_fourcc;
> > u32 color_depth;
>
> Reviewed-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
>
> Would be also good to return the original error code. There is no need
> to check for the < 1 clock, it should be the < 0 check. Can be done in a
> separate patch later. Thanks for the fix!
I'm not very familiar with th edevm_clk_bulk_get_all() function and it's
not documented. But clk_bulk_get_all() does return zero, so I can see why
people would be confused.
regards,
dan carpenter
next prev parent reply other threads:[~2025-03-07 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 9:30 Dan Carpenter
2025-03-07 9:36 ` Dmitry Osipenko
2025-03-07 9:45 ` Dan Carpenter [this message]
2025-03-07 9:47 ` Dmitry Osipenko
2025-03-07 9:58 ` Hans Verkuil
2025-03-07 10:00 ` Dmitry Osipenko
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=4a50949d-e472-4942-9152-3e5a54c6b076@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=dmitry.osipenko@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=shawn.wen@rock-chips.com \
--cc=shreeya.patel@collabora.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®