All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Vincent Jardin" <vjardin@free.fr>
Cc: conor+dt@kernel.org, robh@kernel.org,
	linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v6 3/4] hwmon: pmbus: add MPQ8646 driver
Date: Wed, 29 Jul 2026 22:05:47 +0000	[thread overview]
Message-ID: <20260729220547.C24321F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260729-mpq8646_v0-v6-3-98848151cdb4@free.fr>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Missing named initializers in `struct i2c_device_id` array.
--

--- Patch [3]: [PATCH v6 3/4] hwmon: pmbus: add MPQ8646 driver ---
commit 63fabec4213f8ada1bf01d09967620e66fc9f459
Author: Vincent Jardin <vjardin@free.fr>

hwmon: pmbus: add MPQ8646 driver

This commit adds a new driver for the MPS MPQ8646 PMBus device. It provides
basic PMBus telemetry, alarm acknowledgement, STATUS_WORD extended bit
decoding, NVM-backed post-mortem data, and an in-driver alarm-poll fallback.

> diff --git a/drivers/hwmon/pmbus/mpq8646.c b/drivers/hwmon/pmbus/mpq8646.c
> new file mode 100644
> index 0000000000000..1fd41d89e5bef
> --- /dev/null
> +++ b/drivers/hwmon/pmbus/mpq8646.c
[ ... ]
> +static const struct i2c_device_id mpq8646_id[] = {
> +	{ "mpq8646", 0 },
> +	{ },
> +};

[Severity: Low]
This isn't a bug, but should this array use named initializers? The I2C
subsystem guidelines specify that initialized arrays of type struct
i2c_device_id must use named initializers, such as:
	{ .name = "mpq8646", .driver_data = 0 },

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260729-mpq8646_v0-v6-0-98848151cdb4@free.fr?part=3

  reply	other threads:[~2026-07-29 22:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29 21:51 [PATCH v6 0/4] hwmon: pmbus: add MPS MPQ8646 support Vincent Jardin via B4 Relay
2026-07-29 21:51 ` Vincent Jardin
2026-07-29 21:51 ` [PATCH v6 1/4] hwmon: (pmbus/core) export pmbus_check_and_notify_faults() Vincent Jardin via B4 Relay
2026-07-29 21:51   ` Vincent Jardin
2026-07-29 22:01   ` sashiko-bot
2026-07-29 21:51 ` [PATCH v6 2/4] dt-bindings: hwmon: pmbus: add MPS MPQ8646 Vincent Jardin via B4 Relay
2026-07-29 21:51   ` Vincent Jardin
2026-07-29 22:01   ` sashiko-bot
2026-07-29 21:51 ` [PATCH v6 3/4] hwmon: pmbus: add MPQ8646 driver Vincent Jardin via B4 Relay
2026-07-29 21:51   ` Vincent Jardin
2026-07-29 22:05   ` sashiko-bot [this message]
2026-07-29 21:51 ` [PATCH v6 4/4] hwmon: pmbus: mpq8646: gate the writes Vincent Jardin via B4 Relay
2026-07-29 21:51   ` Vincent Jardin
2026-07-29 22:07   ` sashiko-bot

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=20260729220547.C24321F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=vjardin@free.fr \
    /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.