Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: Eduardo Valentin <eduval@amazon.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
	Eduardo Valentin <eduval@amazon.com>,
	<linux-hwmon@vger.kernel.org>
Subject: Re: [bug report] hwmon: (pmbus) Register with thermal for PSC_TEMPERATURE
Date: Mon, 29 Jul 2024 14:16:25 -0700	[thread overview]
Message-ID: <ZqgGqU3JlRM3RZPS@uf8f119305bce5e.ant.amazon.com> (raw)
In-Reply-To: <d88d5476-eec4-4e0c-8375-18dcc168e31e@suswa.mountain>

Hello,

On Fri, Jul 19, 2024 at 05:33:19PM -0500, Dan Carpenter wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
> 
> 
> 
> On Fri, Jul 19, 2024 at 02:10:16PM -0700, Guenter Roeck wrote:
> > >      1373
> > >      1374         /* temperature sensors with _input values are registered with thermal */
> > > --> 1375         if (class == PSC_TEMPERATURE && strcmp(type, "input") == 0)
> > >                                                          ^^^^
> > > Unchecked dereference
> > >
> >
> > It is only NULL for PSC_PWM, never for PSC_TEMPERATURE. We could add a check to
> > make the static checker happy but it won't make a practical difference.
> 
> No, don't do that.  Just ignore the warning in that case.
> 
> I'm running with the cross function database, and in theory that should
> have silenced the warning.  I'll investigate.

Nice you are doing this, Dan.

Yeah. Let me know the outcome of your investigation. I can always patch it up.

Thanks.

> 
> 
> regards,
> dan carpenter
> 

-- 
All the best,
Eduardo Valentin

      reply	other threads:[~2024-07-29 21:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-19 20:55 [bug report] hwmon: (pmbus) Register with thermal for PSC_TEMPERATURE Dan Carpenter
2024-07-19 21:10 ` Guenter Roeck
2024-07-19 22:33   ` Dan Carpenter
2024-07-29 21:16     ` Eduardo Valentin [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=ZqgGqU3JlRM3RZPS@uf8f119305bce5e.ant.amazon.com \
    --to=eduval@amazon.com \
    --cc=dan.carpenter@linaro.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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