Devicetree
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: Aleksandrs Vinarskis <alex@vinarskis.com>,
	devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v5 1/3] dt-bindings: platform: introduce EC for Dell XPS 13 9345
Date: Wed, 14 Oct 2026 22:05:10 -0500	[thread overview]
Message-ID: <20261015030510.GA282943-robh@kernel.org> (raw)
In-Reply-To: <sashiko-outbox-167353@kernel.org>

On Sun, Oct 11, 2026 at 05:37:21PM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] dt-bindings: architecture-specific header included in yaml example
> --
> 
> commit 8b45bf401f436a6e8330c0e4539c0d77e9e73400
> Author: Aleksandrs Vinarskis <alex@vinarskis.com>
> 
> dt-bindings: platform: introduce EC for Dell XPS 13 9345
> 
> Add bindings for the Embedded Controller in the Dell XPS 13 9345. It defines
> properties for thermal and power management over multiple i2c busses.
> 
> > diff --git a/Documentation/devicetree/bindings/embedded-controller/dell,xps13-9345-ec.yaml b/Documentation/devicetree/bindings/embedded-controller/dell,xps13-9345-ec.yaml
> > new file mode 100644
> > index 0000000000000..3485117b505cc
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/embedded-controller/dell,xps13-9345-ec.yaml
> 
> [ ... ]
> 
> > +examples:
> > +  - |
> > +    #include <dt-bindings/interrupt-controller/irq.h>
> > +    #include <arm64/qcom/qcom-adc5-gen3.h>
> 
> [Severity: Low]
> Does this example include an architecture-specific header? Including headers
> outside of include/dt-bindings/ breaks dt-binding schema portability rules.

Yeah, please don't use arch headers in examples.

Rob

  reply	other threads:[~2026-10-15  3:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-11 17:29 [PATCH v5 0/3] (no cover subject) Aleksandrs Vinarskis
2026-10-11 17:29 ` [PATCH v5 1/3] dt-bindings: platform: introduce EC for Dell XPS 13 9345 Aleksandrs Vinarskis
2026-10-11 17:37   ` sashiko-bot
2026-10-15  3:05     ` Rob Herring [this message]
2026-10-11 17:29 ` [PATCH v5 2/3] platform: arm64: dell-xps-ec: new driver Aleksandrs Vinarskis
2026-10-11 17:42   ` sashiko-bot
2026-10-11 17:29 ` [PATCH v5 3/3] arm64: dts: qcom: x1e80100-dell-xps13-9345: introduce EC Aleksandrs Vinarskis
2026-10-11 17:36   ` 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=20261015030510.GA282943-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=alex@vinarskis.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox