From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Bart Van Assche <bvanassche@acm.org>,
Rob Herring <robh@kernel.org>,
"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Brian Masney <bmasney@redhat.com>,
Nitin Rawat <quic_nitirawa@quicinc.com>,
Can Guo <quic_cang@quicinc.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] scsi: ufs: ufshcd-pltfrm: Signedness bug in ufshcd_parse_clock_info()
Date: Fri, 16 Aug 2024 12:04:04 +0530 [thread overview]
Message-ID: <20240816063404.GH2331@thinkpad> (raw)
In-Reply-To: <6beba3f4-dfa1-4871-829c-ed1e44b5bd39@stanley.mountain>
On Fri, Aug 16, 2024 at 12:35:22AM +0300, Dan Carpenter wrote:
> On Thu, Aug 15, 2024 at 10:47:30AM -0700, Bart Van Assche wrote:
> > On 8/15/24 4:24 AM, Dan Carpenter wrote:
> > > The "sz" variable needs to be a signed type for the error handling to
> > > work as intended.
> >
> > What error handling are you referring to? I haven't found any code that
> > assigns a negative value to 'sz' in ufshcd_parse_clock_info(). Did I
> > perhaps overlook something?
> >
>
> Rob's patch in linux-next.
>
It would've been helpful if you added 'next' in the patch subject prefix.
Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
- Mani
> - if (!of_get_property(np, "freq-table-hz", &len)) {
> + sz = of_property_count_u32_elems(np, "freq-table-hz");
> + if (sz <= 0) {
> dev_info(dev, "freq-table-hz property not specified\n");
> goto out;
>
> regards,
> dan carpenter
>
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2024-08-16 6:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 11:24 [PATCH] scsi: ufs: ufshcd-pltfrm: Signedness bug in ufshcd_parse_clock_info() Dan Carpenter
2024-08-15 17:47 ` Bart Van Assche
2024-08-15 21:35 ` Dan Carpenter
2024-08-16 6:34 ` Manivannan Sadhasivam [this message]
2024-08-16 11:46 ` Dan Carpenter
2024-08-17 1:07 ` Martin K. Petersen
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=20240816063404.GH2331@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bmasney@redhat.com \
--cc=bvanassche@acm.org \
--cc=dan.carpenter@linaro.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=quic_cang@quicinc.com \
--cc=quic_nitirawa@quicinc.com \
--cc=robh@kernel.org \
/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