Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: Ramiro Oliveira <ramiro.oliveira@advantech.com>,
	linux-hwmon@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-watchdog@vger.kernel.org, mfd@lists.linux.dev
Subject: Re: [PATCH v2 1/8] Add Advantech EIO driver
Date: Thu, 16 Jul 2026 12:26:28 +0100	[thread overview]
Message-ID: <20260716112628.GB1260374@google.com> (raw)
In-Reply-To: <20260714160814.3CA9B1F000E9@smtp.kernel.org>

On Tue, 14 Jul 2026, sashiko-bot@kernel.org wrote:

> Thank you for your contribution! Sashiko AI review found 15 potential issue(s) to consider:
> - [Critical] Driver uses zero-initialized `pmc[0]` array without verifying if the primary EC was successfully initialized, causing unintended I/O on system port 0x00.
> - [High] Missing success return for supported legacy code bases in `firmware_code_base()`.
> - [High] Incorrect validation of `devm_ioport_map()` return value.
> - [Medium] The `mfd_cell` array `eio_devs` is not declared as `const`.
> - [Medium] The driver uses `PLATFORM_DEVID_NONE` instead of `PLATFORM_DEVID_AUTO`, risking sysfs naming collisions.
> - [Medium] `acpi_ram_access()` truncates negative error codes into positive 8-bit integers.
> - [Medium] The requested region for the PNP base ports is off-by-one and fails to reserve the data port.
> - [Medium] Missing resource request for the dynamically discovered PMC command port.
> - [Medium] Unaligned memory access and endianness assumptions in `info_show()`.
> - [Medium] The IO port memory mapping is sized statically up to `0x49A`, but accesses dynamically discovered hardware registers which can exceed the mapped bounds.
> - [Medium] `pmc_clear` checks the wrong status bit (`IBF` instead of `OBF`) before attempting to clear pending garbage data.
> - [Medium] Hardware PNP configuration mode is left unlocked on error and skip paths in `eio_init()`.
> - [Low] The commit message prefix violates MFD subsystem naming conventions.
> - [Low] `MFD_EIO` uses the `isa_driver` API but lacks a Kconfig dependency on `ISA_BUS_API`.
> - [Low] Driver-specific header file is improperly placed in the global `include/linux/mfd/` directory.

That should keep you busy for a while.

Dropping this from my queue.

-- 
Lee Jones

  reply	other threads:[~2026-07-16 11:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 15:54 [PATCH v2 0/8] Add support for Advantech EIO MFD series devices Ramiro Oliveira
2026-07-14 15:54 ` [PATCH v2 1/8] Add Advantech EIO driver Ramiro Oliveira
2026-07-14 16:08   ` sashiko-bot
2026-07-16 11:26     ` Lee Jones [this message]
2026-07-14 15:54 ` [PATCH v2 2/8] Add Advantech EIO GPIO driver Ramiro Oliveira
2026-07-14 16:06   ` sashiko-bot
2026-07-15 12:24   ` Bartosz Golaszewski
2026-07-14 15:54 ` [PATCH v2 3/8] Add Advantech EIO Hardware Monitor driver Ramiro Oliveira
2026-07-14 16:05   ` sashiko-bot
2026-07-16  0:29   ` Guenter Roeck
2026-07-16  8:10     ` Ramiro Manuel Silva Oliveira
2026-07-16 11:36       ` Guenter Roeck
2026-07-14 15:54 ` [PATCH v2 4/8] Add Advantech EIO I2C driver Ramiro Oliveira
2026-07-14 16:11   ` sashiko-bot
2026-07-14 15:54 ` [PATCH v2 5/8] Add Advantech EIO Backlight driver Ramiro Oliveira
2026-07-14 16:05   ` sashiko-bot
2026-07-14 15:54 ` [PATCH v2 6/8] Add Advantech EIO Watchdog driver Ramiro Oliveira
2026-07-14 16:07   ` sashiko-bot
2026-07-14 15:54 ` [PATCH v2 7/8] Add Advantech EIO Thermal driver Ramiro Oliveira
2026-07-14 16:05   ` sashiko-bot
2026-07-14 15:54 ` [PATCH v2 8/8] Add Advantech EIO Fan driver Ramiro Oliveira
2026-07-14 16:14   ` 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=20260716112628.GB1260374@google.com \
    --to=lee@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=mfd@lists.linux.dev \
    --cc=ramiro.oliveira@advantech.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox