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
| ||
|
Date: Mon, 20 Jul 2015 17:48:40 -0700 From: Joe Perches <joe@...ches.com> To: paulmck@...ux.vnet.ibm.com Cc: linux-kernel@...r.kernel.org, mingo@...nel.org, laijs@...fujitsu.com, dipankar@...ibm.com, akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com, josh@...htriplett.org, tglx@...utronix.de, peterz@...radead.org, rostedt@...dmis.org, dhowells@...hat.com, edumazet@...gle.com, dvhart@...ux.intel.com, fweisbec@...il.com, oleg@...hat.com, bobby.prani@...il.com, Andy Whitcroft <apw@...onical.com> Subject: Re: [PATCH tip/core/rcu 15/16] scripts: Make checkpatch.pl warn on expedited RCU grace periods On Mon, 2015-07-20 at 17:41 -0700, Paul E. McKenney wrote: > On Fri, Jul 17, 2015 at 03:37:54PM -0700, Joe Perches wrote: > > It'd be faster perl without capture groups: > > > > if ($line =~ /\b(?:synchronize_(?:rcu|sched)_expedited)\s*\(/) { > > Fair enough, but this pattern is used rather heavily in this script, > and I don't trust my perl enough to want to create a new pattern. > > I see a couple of possible ways forward: > > 1. I hand this patch off to you, and you update it as you deem fit. > > 2. I push the patch as is (after the fix below) and you update > checkpatch as a whole to use the more efficient code. > > How would you like to proceed? Push and fix would work fine. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists