From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: "Théo Lebrun" <theo.lebrun@bootlin.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Yuanjun Gong <ruc_gongyuanjun@163.com>,
Andi Shyti <andi.shyti@kernel.org>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH 1/1] drivers/i2c: fix a potential null pointer dereference
Date: Wed, 14 May 2025 17:05:56 +0200 [thread overview]
Message-ID: <aCSxVFMOAg070xHW@shikoro> (raw)
In-Reply-To: <D9VS2G7S3T9Q.26QDCDRTC2S11@bootlin.com>
[-- Attachment #1: Type: text/plain, Size: 236 bytes --]
> > Also including Theo on this, he is the major industrial user of this driver now.
>
> Thanks for the Cc; I agree with your reading of the code and don't see
> the issue.
Likely a false positive from static code analysis.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2025-05-14 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 12:37 [PATCH 1/1] drivers/i2c: fix a potential null pointer dereference Yuanjun Gong
2025-05-13 22:10 ` Linus Walleij
2025-05-14 9:31 ` Théo Lebrun
2025-05-14 15:05 ` Wolfram Sang [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=aCSxVFMOAg070xHW@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=andi.shyti@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=ruc_gongyuanjun@163.com \
--cc=theo.lebrun@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.