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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2025082139-bullion-canopy-e705@gregkh>
Date: Thu, 21 Aug 2025 16:49:27 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Carlos Llamas <cmllamas@...gle.com>, Alice Ryhl <aliceryhl@...gle.com>,
	Arve Hjønnevåg <arve@...roid.com>,
	Todd Kjos <tkjos@...roid.com>, Martijn Coenen <maco@...roid.com>,
	Joel Fernandes <joelagnelf@...dia.com>,
	Christian Brauner <brauner@...nel.org>,
	Suren Baghdasaryan <surenb@...gle.com>,
	Donald Hunter <donald.hunter@...il.com>,
	"David S. Miller" <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
	Simon Horman <horms@...nel.org>, Li Li <dualli@...gle.com>,
	Tiffany Yang <ynaffit@...gle.com>, John Stultz <jstultz@...gle.com>,
	kernel-team@...roid.com, linux-kernel@...r.kernel.org,
	Thorsten Leemhuis <linux@...mhuis.info>,
	"open list:NETWORKING [GENERAL]" <netdev@...r.kernel.org>
Subject: Re: [PATCH] netlink: specs: binder: replace underscores with dashes
 in names

On Thu, Aug 21, 2025 at 07:37:43AM -0700, Jakub Kicinski wrote:
> On Thu, 21 Aug 2025 13:55:21 +0000 Carlos Llamas wrote:
> > The usage of underscores is no longer allowed for the 'name' format in
> > the yaml spec. Instead, dashes should be used. This fixes the build
> > issue reported by Thorsten that showed up on linux-next.
> > 
> > Note this change has no impact on C code.
> 
> I guess the tree where the patches landed doesn't have last merge window
> material? I thought the extra consistency checks went in for 6.17
> already.. In any case, change makes sense:

They don't seem to be in 6.17-rc3, what commit are you thinking this
was?  Ugh, my fault, nevermind, I was testing the wrong branch in the
wrong git tree!

I see this in my tree now, sorry everyone for the noise in not figuring
this out, too many trees/branches...

> Reviewed-by: Jakub Kicinski <kuba@...nel.org>

Thanks, I'll take this in the char-misc-next branch now.

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ