mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Jassi Brar <jassisinghbrar@gmail.com>
Cc: linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mark Brown <broonie@linaro.org>
Subject: Re: [PATCH 1/2] mailbox: add sanity check for channel array
Date: Sun, 19 Apr 2026 01:57:22 +0200	[thread overview]
Message-ID: <aeQaYmXr8XV9r3ME@shikoro> (raw)
In-Reply-To: <CABb+yY0NrmCRu7c3Y0JiahmVCNCq-B57TckQC++X=HY6bL0-sQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 824 bytes --]


> This sounds like a quick suggestion from some AI tool -- looks nice
> but doesn't mean much.

Nope, from the cover letter:

While diving deeper into this subsystem, I manually found these two
issues which I wanted to fix right away.

I just wanted to check which parameters are required and which are
optional. And the array is definitely required, so the core should check
for it IMHO.

> point to an array of channels. NULL is just another garbage value, why
> not also check for 0xdeadbabe or 0xffff... ?

Because NULL is what we get if we kzalloc a structure unlike the values
you mentioned.

> I can let loose a claude session and I will find 1000s of such "fixes"
> in the kernel.

No AI was involved in the generation of these patches. I think I marked
the patches which resulted from AI review correctly so far.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-04-18 23:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13 10:42 [PATCH 0/2] mailbox: improvments around registering controllers Wolfram Sang
2026-04-13 10:42 ` [PATCH 1/2] mailbox: add sanity check for channel array Wolfram Sang
2026-04-16 13:25   ` Geert Uytterhoeven
2026-04-18 18:00   ` Jassi Brar
2026-04-18 23:57     ` Wolfram Sang [this message]
2026-04-19  1:36       ` Jassi Brar
2026-04-13 10:42 ` [PATCH 2/2] mailbox: update kdoc for struct mbox_controller Wolfram Sang
2026-04-16 13:29   ` Geert Uytterhoeven
2026-04-18 19:44     ` Jassi Brar

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=aeQaYmXr8XV9r3ME@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=broonie@linaro.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@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®