All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Jardin <vjardin@free.fr>
To: Guenter Roeck <linux@roeck-us.net>
Cc: sashiko-reviews@lists.linux.dev, linux-hwmon@vger.kernel.org,
	conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 3/3] hwmon: pmbus: add MPQ8646 driver
Date: Fri, 24 Jul 2026 12:04:39 +0200	[thread overview]
Message-ID: <amM4t3Mr-TcEiQgB@L30177.local> (raw)
In-Reply-To: <b5c0741a-b9da-4a3a-81ae-33368e6dd756@roeck-us.net>

Hi,

> > Although this is triggered via debugfs, executing it on a DMA-capable I2C bus
> > could reliably crash or corrupt the system. Should these buffers be dynamically
> > allocated instead?
> > 
> 
> Do not address. This is a false positive. Sashiko's I2C subsystem prompts
> need to be updated.

thanks Guenter for this guideline.

Very appreciated,
  Vincent

  reply	other threads:[~2026-07-24 10:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23 23:55 [PATCH v5 0/3] hwmon: pmbus: add MPS MPQ8646 support Vincent Jardin via B4 Relay
2026-07-23 23:55 ` Vincent Jardin
2026-07-23 23:55 ` [PATCH v5 1/3] hwmon: pmbus: event notification with alarms Vincent Jardin via B4 Relay
2026-07-23 23:55   ` Vincent Jardin
2026-07-24  0:10   ` sashiko-bot
2026-07-23 23:55 ` [PATCH v5 2/3] dt-bindings: hwmon: pmbus: add MPS MPQ8646 binding Vincent Jardin via B4 Relay
2026-07-23 23:55   ` Vincent Jardin
2026-07-24  0:02   ` sashiko-bot
2026-07-23 23:55 ` [PATCH v5 3/3] hwmon: pmbus: add MPQ8646 driver Vincent Jardin via B4 Relay
2026-07-23 23:55   ` Vincent Jardin
2026-07-24  0:06   ` sashiko-bot
2026-07-24  2:07     ` Guenter Roeck
2026-07-24 10:04       ` Vincent Jardin [this message]
2026-07-24  2:15   ` Guenter Roeck
2026-07-24 10:18     ` Vincent Jardin
2026-07-24 13:23       ` Guenter Roeck
2026-07-24 14:00   ` Guenter Roeck

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=amM4t3Mr-TcEiQgB@L30177.local \
    --to=vjardin@free.fr \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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.