All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: Kanak Shilledar <kanak.shilledar@axis.com>,
	conor+dt@kernel.org,  robh@kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: Add InvenSense ICM-42370-p accelerometer
Date: Tue, 18 Aug 2026 09:51:47 +0200	[thread overview]
Message-ID: <20260818-rustling-grebe-of-expression-fd9a1e@quoll> (raw)
In-Reply-To: <20260813123421.3AC681F000E9@smtp.kernel.org>

On Thu, Aug 13, 2026 at 12:34:20PM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
> - [Medium] Incomplete device tree binding schema rejects valid hardware configurations for SPI, I3C, and reset lines.
> - [Low] Missing IIO subsystem mailing list in MAINTAINERS entry.

What? This is just ridicilous and wrong advice.

Best regards,
Krzysztof


  reply	other threads:[~2026-08-18  7:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13 12:26 [PATCH v2 0/3] Add driver for Invensense ICM42370P accelerometer Kanak Shilledar
2026-08-13 12:26 ` [PATCH v2 1/3] dt-bindings: Add InvenSense ICM-42370-p accelerometer Kanak Shilledar
2026-08-13 12:34   ` sashiko-bot
2026-08-18  7:51     ` Krzysztof Kozlowski [this message]
2026-08-18  7:56   ` Krzysztof Kozlowski
2026-08-13 12:26 ` [PATCH v2 2/3] iio: accel: Add support for ICM42370P Kanak Shilledar
2026-08-13 12:41   ` sashiko-bot
2026-08-16  2:59   ` Jonathan Cameron
2026-08-24  9:33     ` Kanak Shilledar
2026-08-13 12:26 ` [PATCH v2 3/3] iio: accel: icm42370: Add FIFO buffer functionality Kanak Shilledar
2026-08-13 12:40   ` sashiko-bot
2026-08-16  3:12   ` Jonathan Cameron
2026-08-17  9:48   ` Joshua Crofts
2026-08-17  7:19 ` [PATCH v2 0/3] Add driver for Invensense ICM42370P accelerometer Andy Shevchenko
2026-08-20 14:02   ` Kanak Shilledar
2026-08-20 15:19 ` Jean-Baptiste Maneyrol
2026-08-24  9:38   ` Kanak Shilledar

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=20260818-rustling-grebe-of-expression-fd9a1e@quoll \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kanak.shilledar@axis.com \
    --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.