From: James Bottomley <James.Bottomley@SteelEye.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Parisc List <parisc-linux@lists.parisc-linux.org>
Subject: [parisc-linux] Re: Another problem with making things static
Date: Sat, 10 Feb 2007 19:33:21 -0600 [thread overview]
Message-ID: <1171157601.3373.40.camel__27397.8429534056$1416624279$gmane$org@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <20070210130130.2584e4d8.akpm@linux-foundation.org>
On Sat, 2007-02-10 at 13:01 -0800, Andrew Morton wrote:
> On Sat, 10 Feb 2007 09:29:24 -0600 James Bottomley <James.Bottomley@SteelEye.com> wrote:
>
> > For any person who wants to make a static symbol exported, we force an
> > explanation out of them about what they're trying to do and why. Might
> > I suggest we apply the same standard to anyone trying to make something
> > static? i.e. they need to explain clearly why the symbol shouldn't be
> > part of any rational API.
> >
>
> The majority of these things are simply oversights: people forgot to
> type `static'.
>
> C got the defualt wrong..
I agree ... lots of symbols in drivers or filesystems are obviously not
part of APIs ... however, that's not necessarily true of the kernel
proper. I think forcing someone to think about what they're doing and
justify going from non static to static or vice versa is a good idea in
those cases.
James
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
prev parent reply other threads:[~2007-02-11 1:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1171121364.3373.19.camel@mulgrave.il.steeleye.com>
2007-02-10 21:01 ` [parisc-linux] Re: Another problem with making things static Andrew Morton
[not found] ` <20070210130130.2584e4d8.akpm@linux-foundation.org>
2007-02-11 1:33 ` James Bottomley [this message]
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='1171157601.3373.40.camel__27397.8429534056$1416624279$gmane$org@mulgrave.il.steeleye.com' \
--to=james.bottomley@steeleye.com \
--cc=akpm@linux-foundation.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.