All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Waychison <Michael.Waychison@Sun.COM>
To: arjanv@redhat.com
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] export complete_all
Date: Thu, 25 Mar 2004 11:20:08 -0500	[thread overview]
Message-ID: <406306B8.90303@sun.com> (raw)
In-Reply-To: <1080200277.5225.2.camel@laptop.fenrus.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Arjan van de Ven wrote:
| On Wed, 2004-03-24 at 23:50, Mike Waychison wrote:
|
|>-----BEGIN PGP SIGNED MESSAGE-----
|>Hash: SHA1
|>
|>No idea why it hasn't been done already, but complete_all wasn't
|>exported while complete was.
|
|
| which module is using this ?

None at the moment, so getting this applied isn't neccesarily a high
priority.  Actually, the only in-tree caller is fs/exec.c:do_coredump.

I'm currently working on writing a new autofs stack and will eventually
~ need this call exported.  It seems strange to me that we'd only export
portions of an api like this.


- --
Mike Waychison
Sun Microsystems, Inc.
1 (650) 352-5299 voice
1 (416) 202-8336 voice
mailto: Michael.Waychison@Sun.COM
http://www.sun.com

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE:  The opinions expressed in this email are held by me,
and may not represent the views of Sun Microsystems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAYwa3dQs4kOxk3/MRAo5vAJ423HBBuES9xxzWOUW5Ms+jWUtfGwCgkoIf
V3yDiSgsetl5A4pOUdRvkXQ=
=/zUy
-----END PGP SIGNATURE-----

      parent reply	other threads:[~2004-03-25 16:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-24 22:50 [PATCH] export complete_all Mike Waychison
     [not found] ` <1080200277.5225.2.camel@laptop.fenrus.com>
2004-03-25 16:20   ` Mike Waychison [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=406306B8.90303@sun.com \
    --to=michael.waychison@sun.com \
    --cc=akpm@osdl.org \
    --cc=arjanv@redhat.com \
    --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 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.