mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: mike@waychison.com, bunk@stusta.de, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] unexport complete_all
Date: Fri, 4 Mar 2005 03:15:04 -0800	[thread overview]
Message-ID: <20050304031504.4ea49f83.akpm@osdl.org> (raw)
In-Reply-To: <58cb370e0503040240314120ea@mail.gmail.com>

Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
>
> Andrew, what is the policy for adding exports for out of tree GPL code?
> 

There isn't one.  Such things cause way too much email.

What complete_all() does is to permit more than one task to wait on a
completion and for all those tasks to be woken by a single complete(). 
Without it you'd need to record how many tasks are sleeping there and do
complete() that many times.

So it's a sensible part of the completion API from a regularity-of-the-API
POV.  We use it in the coredump code and I don't think we'd be likely to want
to rip it out.

In fact, I'd say that complete() should have always done it this way...


  parent reply	other threads:[~2005-03-04 12:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04  8:09 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 [this message]
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
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=20050304031504.4ea49f83.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=bzolnier@gmail.com \
    --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

Powered by JetHome