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: [rfc 0/2] pinctrl property checks
Date: Wed, 4 Feb 2026 14:11:20 +0000 [thread overview]
Message-ID: <20260204-twentieth-facedown-55eca3d3022c@spud> (raw)
In-Reply-To: <CAD++jLnz1r1gnE3B_0MCr0JrfEdT-74nM7wL3ErdrmzHOrnovQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
On Wed, Feb 04, 2026 at 12:30:30AM +0100, Linus Walleij wrote:
> On Tue, Feb 3, 2026 at 6:30 PM Conor Dooley <conor@kernel.org> wrote:
>
> > Finally got around to sending the property stuff that we were talking
> > about. It's definitely not the best thing I have ever written, but I
> > think it does an okay job of warning about setups that don't make sense
> > while adding fairly little complexity wise.
>
> I like what I see and I think we should apply it for the v7.1 kernel cycle
> post v7.0-rc1.
>
> Are you ready to send a non-RFC version by then?
The rfc tag is was more because of the point in the cycle we are at than
the question on the driver patch. Sending a non-rtc then should be no
problem.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-02-04 14:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 17:29 [rfc 0/2] pinctrl property checks Conor Dooley
2026-02-03 17:29 ` [rfc 1/2] pinctrl: pinconf-generic: perform basic checks on pincfg properties Conor Dooley
2026-02-03 17:29 ` [rfc 2/2] dt-bindings: pinctrl: pincfg-node: add restrictions on conflicting properties Conor Dooley
2026-02-03 23:30 ` [rfc 0/2] pinctrl property checks Linus Walleij
2026-02-04 14:11 ` 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=20260204-twentieth-facedown-55eca3d3022c@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