From: Diego Calleja <diegocg@gmail.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] scsi_transport_spi.c: make print_nego() static
Date: Sat, 7 Jan 2006 02:26:25 +0100 [thread overview]
Message-ID: <20060107022625.e2c1dc0f.diegocg@gmail.com> (raw)
In-Reply-To: <20060105223918.GM12313@stusta.de>
El Thu, 5 Jan 2006 23:39:18 +0100,
Adrian Bunk <bunk@stusta.de> escribió:
> This patch makes a needlessly global function static.
Ok, so this is probably a stupid question and it may have been already
discussed but.....
Isn't possible that GCC would/will add an extension (a useful one) similar
to the visibility thing that c++ got in GCC 4.x? It somewhat weird
that we need to mark things static, instead of the contrary (marking
as global the things you want to make global, would be much nicer since
the functions made global would be the "API")
next prev parent reply other threads:[~2006-01-07 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 22:39 [2.6 patch] scsi_transport_spi.c: make print_nego() static Adrian Bunk
2006-01-05 22:44 ` Matthew Wilcox
2006-01-07 1:26 ` Diego Calleja [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-14 2:09 Adrian Bunk
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=20060107022625.e2c1dc0f.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.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