[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.22.394.2312192218050.3196@hadrien>
Date: Tue, 19 Dec 2023 22:21:25 +0100 (CET)
From: Julia Lawall <julia.lawall@...ia.fr>
To: Luis Chamberlain <mcgrof@...nel.org>
cc: Thomas Weißschuh <linux@...ssschuh.net>,
Julia Lawall <julia.lawall@...ia.fr>,
Joel Granados <j.granados@...sung.com>,
Dan Carpenter <dan.carpenter@...aro.org>,
Kees Cook <keescook@...omium.org>,
"Gustavo A. R. Silva" <gustavoars@...nel.org>,
Iurii Zaikin <yzaikin@...gle.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-hardening@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH v2 00/18] sysctl: constify sysctl ctl_tables
> As I noted, I think this is a generically neat endeavor and so I think
> it would be nice to shorthand *any* member of the struct. ctl->any.
> Julia, is that possible?
What do you mean by *any* member? If any is an identifier typed
metavariable then that would get any immediate member. But maybe you want
something like
<+...ctl->any...+>
that will match anything that has ctl->any as a subexpression?
It may be necessary to put this in parentheses to address parsing issues,
but the () won't need to be present in the matched code.
You could also use
assignment operator aop;
rather than =, to also match += etc.
julia
Powered by blists - more mailing lists