From: Julia Lawall <julia@diku.dk>
To: Joe Perches <joe@perches.com>
Cc: Ingo Molnar <mingo@elte.hu>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Am??rico Wang <xiyou.wangcong@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] sysctl.c: Change a .proc_handler = proc_dointvec to &proc_dointvec,
Date: Sun, 15 Nov 2009 21:40:25 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0911152139020.30372@ask.diku.dk> (raw)
In-Reply-To: <1258313031.21668.73.camel@Joe-Laptop.home>
On Sun, 15 Nov 2009, Joe Perches wrote:
> On Sun, 2009-11-15 at 19:20 +0100, Julia Lawall wrote:
> > Searching for things that are declared as functions (either a definition
> > or a prototype), and then referenced as &f gives over 2000 results in
> > almost 600 files.
>
> Just curious, do you know how many are referenced
> without the &?
I got over 95000 (not checked in detail, though).
> > Here are a couple of typical examples:
> >
> > arch/arm/mach-omap1/clock.c:
> >
> > static const struct clkops clkops_dspck = {
> > .enable = &omap1_clk_enable_dsp_domain,
> > .disable = &omap1_clk_disable_dsp_domain,
> > };
> >
> > arch/arm/mach-omap1/serial.c:
> >
> > ret = request_irq(gpio_to_irq(gpio_nr), &omap_serial_wake_interrupt,
> > IRQF_TRIGGER_RISING, "serial wakeup", NULL);
> >
> > Should both cases lose the initial &?
>
> If what is desired is kernel wide consistent use, yes.
> What I would like is file/subsystem consistent use.
>
> Looking at sysctl.c and seeing that different use
> stand out was odd.
It would be possible to count the number of occurrences in a given file,
and then change the ones that have the less popular format, or a format
that occurs less than some percentage of time.
julia
next prev parent reply other threads:[~2009-11-15 20:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-15 1:52 Joe Perches
2009-11-15 6:59 ` Américo Wang
2009-11-15 8:11 ` Ingo Molnar
2009-11-15 8:28 ` Joe Perches
2009-11-15 8:39 ` Ingo Molnar
2009-11-15 10:04 ` Eric W. Biederman
2009-11-15 10:33 ` Ingo Molnar
2009-11-15 12:29 ` Eric W. Biederman
2009-11-15 13:57 ` Ingo Molnar
2009-11-15 14:14 ` Eric W. Biederman
2009-11-15 17:31 ` Joe Perches
2009-11-15 18:20 ` Julia Lawall
2009-11-15 19:23 ` Joe Perches
2009-11-15 20:40 ` Julia Lawall [this message]
2009-11-15 20:53 ` Arnd Bergmann
2009-11-15 22:54 ` Julia Lawall
2009-11-15 21:13 ` Joe Perches
2009-11-15 21:34 ` Julia Lawall
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=Pine.LNX.4.64.0911152139020.30372@ask.diku.dk \
--to=julia@diku.dk \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=xiyou.wangcong@gmail.com \
/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
all inboxes | Powered by JetHome®