lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20260204-twentieth-facedown-55eca3d3022c@spud>
Date: Wed, 4 Feb 2026 14:11:20 +0000
From: Conor Dooley <conor@...nel.org>
To: Linus Walleij <linusw@...nel.org>
Cc: Conor Dooley <conor.dooley@...rochip.com>,
	Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>, linux-gpio@...r.kernel.org,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [rfc 0/2] pinctrl property checks

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@...nel.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.

Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ