From: Markus Elfring <Markus.Elfring@web.de>
To: Elad Nachman <enachman@marvell.com>, linux-i2c@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Andi Shyti <andi.shyti@kernel.org>,
Gregory Clement <gregory.clement@bootlin.com>
Subject: Re: [PATCH] i2c: mv64xxx: prevent illegal pointer access
Date: Tue, 29 Jul 2025 20:56:11 +0200 [thread overview]
Message-ID: <27916016-674b-476e-99c4-a5f7d53632a6@web.de> (raw)
In-Reply-To: <20250729084523.3220002-1-enachman@marvell.com>
…
> Add check to verify buffer pointer is not NULL before
> reading or writing the buffer for additional TX or RX
> operations.
You may occasionally put more than 53 characters into text lines
of such a change description.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.16#n658
Regards,
Markus
prev parent reply other threads:[~2025-07-29 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 8:45 enachman
2025-07-29 18:56 ` Markus Elfring [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=27916016-674b-476e-99c4-a5f7d53632a6@web.de \
--to=markus.elfring@web.de \
--cc=andi.shyti@kernel.org \
--cc=enachman@marvell.com \
--cc=gregory.clement@bootlin.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®