mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Mike Frysinger <vapier@gentoo.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] headers_check.pl: disallow extern's
Date: Fri, 2 Jan 2009 16:05:25 -0800	[thread overview]
Message-ID: <20090102160525.430c59f9@infradead.org> (raw)
In-Reply-To: <200901030059.18438.arnd@arndb.de>

On Sat, 3 Jan 2009 00:59:18 +0100
Arnd Bergmann <arnd@arndb.de> wrote:

> On Wednesday 31 December 2008, Mike Frysinger wrote:
> > On Wednesday 31 December 2008 11:58:03 Arnd Bergmann wrote:
> >
> > > Not sure if we can detect the other form reliably from perl.
> > 
> > yes, i already mentioned both of these issues.  that's why i
> > suggested we start adding "extern" to all the headers (or at least
> > the userspace ones).
> 
> The general trend seems to be to remove the "extern" keyword from
> kernel headers, because it is not interpreted, just like the 'auto'
> keyword. In fact, only few of them currently carry the extern keyword:
> 
> $ ctags -f- -R --c-kinds=p obj/usr/include/  | grep extern | wc -l
> 33
> 
> $ ctags -f- -R --c-kinds=p obj/usr/include/  | grep -v extern | wc -l
> 191
> 
> Note that this is a completely separate issue from extern variable
> declarations, which should to be disallowed in any case, and are easy
> to detect as they always require the extern keyword.

in addition... what business does the kernel have to provide function
prototypes to userspace, other than the system call prototypes?


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2009-01-03  0:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-27  7:43 Mike Frysinger
2008-12-27 18:43 ` Sam Ravnborg
2008-12-27 18:54   ` Sam Ravnborg
2008-12-27 19:21     ` Mike Frysinger
2008-12-29 10:15     ` Mike Frysinger
2008-12-29 12:00       ` Sam Ravnborg
2008-12-27 19:23   ` Mike Frysinger
2008-12-31 16:58 ` Arnd Bergmann
2008-12-31 22:32   ` Mike Frysinger
2009-01-02 23:59     ` Arnd Bergmann
2009-01-03  0:05       ` Arjan van de Ven [this message]
2009-01-03  0:09         ` Arnd Bergmann
2009-01-03  1:20           ` Mike Frysinger
2009-01-03  1:40             ` Arnd Bergmann
2009-01-03  1:51 ` Nigel Cunningham

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=20090102160525.430c59f9@infradead.org \
    --to=arjan@infradead.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=vapier@gentoo.org \
    /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®