From: Sam Ravnborg <sam@ravnborg.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>, Andy Whitcroft <apw@shadowen.org>,
linux-kernel@vger.kernel.org
Subject: Re: checkpatch and kernel/sched.c
Date: Mon, 1 Oct 2007 09:50:14 +0200 [thread overview]
Message-ID: <20071001075014.GB23965@uranus.ravnborg.org> (raw)
In-Reply-To: <20071001003007.4e90143b.akpm@linux-foundation.org>
> >
> > > WARNING: externs should be avoided in .c files
> > > #6545: FILE: home/apw/git/linux-2.6/kernel/sched.c:6542:
> > > + extern char __sched_text_start[], __sched_text_end[];
> > >
> > > That one ... dunno. This check is a difficult one. Should it be a
> > > CHECK?
> >
> > no, this is a legitimate warning - externs in .c files should move into
> > the proper .h file. So i'd suggest to keep this a WARNING.
>
> Yes. When the symbol is defined in .S or vmlinux.lds we have
> traditionally declared it in .c.
>
> But why? It _is_ a global symbol. We might as well declare it in .h.
> That's consistent, and prevents duplicated declarations from popping up
> later on.
It would be nice to collect all linker symbol externs in one place..
asm-$(ARCH)/???.h
We could even auto-generate it but thats not worth it I think.
Sam
next prev parent reply other threads:[~2007-10-01 7:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070928105345.GC18163@shadowen.org>
2007-10-01 6:44 ` Ingo Molnar
2007-10-01 7:30 ` Andrew Morton
2007-10-01 7:48 ` Avi Kivity
2007-10-01 7:39 ` Andrew Morton
2007-10-01 10:39 ` Ingo Molnar
2007-10-01 7:50 ` Sam Ravnborg [this message]
2007-10-01 10:37 ` Ingo Molnar
2007-10-01 10:44 ` Ingo Molnar
2007-10-01 12:34 ` Andy Whitcroft
2007-10-02 4:34 ` Willy Tarreau
2007-10-02 5:18 ` [patch] printk: add KERN_CONT annotation Ingo Molnar
2007-10-02 10:04 ` Jörn Engel
2007-10-02 15:41 ` Joe Perches
2007-10-02 15:45 ` Jan Engelhardt
2007-10-02 16:03 ` Joe Perches
2007-10-02 16:07 ` Jan Engelhardt
2007-10-04 20:43 ` Andrew Morton
2007-10-04 20:52 ` Ingo Molnar
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=20071001075014.GB23965@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome