From: Adrian Bunk <bunk@stusta.de>
To: Mike Waychison <mike@waychison.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.6 patch] unexport complete_all
Date: Fri, 4 Mar 2005 12:05:56 +0100 [thread overview]
Message-ID: <20050304110556.GC3992@stusta.de> (raw)
In-Reply-To: <422817C3.2010307@waychison.com>
On Fri, Mar 04, 2005 at 03:09:39AM -0500, Mike Waychison wrote:
> > I didn't find any possible modular usage in the kernel.
> >
> > Signed-off-by: Adrian Bunk <bunk@stusta.de>
> >
> > --- linux-2.6.11-rc5-mm1-full/kernel/sched.c.old 2005-03-04 01:04:28.000000000 +0100
> > +++ linux-2.6.11-rc5-mm1-full/kernel/sched.c 2005-03-04 01:04:34.000000000 +0100
> > @@ -3053,7 +3053,6 @@
> > 0, 0, NULL);
> > spin_unlock_irqrestore(&x->wait.lock, flags);
> > }
> > -EXPORT_SYMBOL(complete_all);
> >
> > void fastcall __sched wait_for_completion(struct completion *x)
> > {
> > -
>
> This is a valid piece of API that is exported for future use.
>...
You exported this function nearly one year ago with the only comment
"Export complete_all for module use.".
Why did you add the export last year instead of simply adding it when it
will be required?
> Mike Waychison
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-03-04 11:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 8:09 [2.6 patch] unexport complete_all Mike Waychison
2005-03-04 10:40 ` Bartlomiej Zolnierkiewicz
2005-03-04 11:07 ` Adrian Bunk
2005-03-04 17:08 ` mike
2005-03-04 20:41 ` Adrian Bunk
2005-03-04 11:15 ` Andrew Morton
2005-03-04 13:14 ` Bartlomiej Zolnierkiewicz
2005-03-08 8:24 ` Bartlomiej Zolnierkiewicz
2005-03-04 13:18 ` Adrian Bunk
2005-03-04 12:55 ` Alan Cox
2005-03-04 11:05 ` Adrian Bunk [this message]
2005-03-04 16:58 ` mike
-- strict thread matches above, loose matches on Subject: below --
2005-03-04 0:47 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=20050304110556.GC3992@stusta.de \
--to=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@waychison.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