Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Linus Walleij <linusw@kernel.org>
Cc: Conor Dooley <conor.dooley@microchip.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH v2 0/2] pinctrl property checks
Date: Sat, 28 Feb 2026 00:41:49 +0000	[thread overview]
Message-ID: <20260228-donated-virtuous-c18dde170111@spud> (raw)
In-Reply-To: <CAD++jLnNPudpxYd8-rNTAudqX2-apM6uZLyBRYxagwtT+LqeaA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 958 bytes --]

On Thu, Feb 26, 2026 at 11:47:33PM +0100, Linus Walleij wrote:
> On Tue, Feb 24, 2026 at 2:39 PM Conor Dooley <conor.dooley@microchip.com> wrote:
> 
> > Here's a !rfc version of these property checks. Nothing has changed here
> > outside of a rebase on v7.0-rc1.
> >
> > Resending because I managed to lose the CC list on all but the cover.
> 
> I applied these for next because why not! People have ample
> time to test them now.

I did not run a check at any point of all the arm or arm64 devicetrees,
I may go do that tomorrow and see if anything pops up. What's more
interesting is if someone comes along with the runtime warnings I think.

> (Dropped an extraneous newline in the first patch.)

I blame conflict resolution from my rebase for that one ;)

Thanks for grabbing it. I still owe you a generic function to replace
the amlogic one that I moved, but I have been busy and not picked up one
of the spacemit k1 boards yet.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2026-02-28  0:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-24 13:39 [RESEND PATCH v2 0/2] pinctrl property checks Conor Dooley
2026-02-24 13:39 ` [RESEND PATCH v2 1/2] pinctrl: pinconf-generic: perform basic checks on pincfg properties Conor Dooley
2026-02-24 13:39 ` [RESEND PATCH v2 2/2] dt-bindings: pinctrl: pincfg-node: add restrictions on conflicting properties Conor Dooley
2026-03-06 23:41   ` Rob Herring
2026-02-26 22:47 ` [RESEND PATCH v2 0/2] pinctrl property checks Linus Walleij
2026-02-28  0:41   ` Conor Dooley [this message]

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=20260228-donated-virtuous-c18dde170111@spud \
    --to=conor@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    /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