All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Jeremy Kerr <jk@ozlabs.org>
Cc: <linux-kernel@vger.kernel.org>, <cbe-oss-dev@ozlabs.org>
Subject: Re: [RFC/PATCH] Export force_sig_info
Date: Thu, 22 Nov 2007 23:41:41 -0800	[thread overview]
Message-ID: <20071122234141.087743fa.akpm@linux-foundation.org> (raw)
In-Reply-To: <1194845812.531937.269801315194.qpush@pokey>

On Mon, 12 Nov 2007 16:36:52 +1100 Jeremy Kerr <jk@ozlabs.org> wrote:

> This change allows force_sig_info to be called from modules.
> 
> Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
> 
> --
> 
> Any objections to exporting this symbol? I'm  planning to move some
> SPU fault-handling code from the kernel to the spufs.ko object.
> 
> ---
> 
>  kernel/signal.c |    1 +
>  1 file changed, 1 insertion(+)
> 
> Index: linux-2.6-spufs/kernel/signal.c
> ===================================================================
> --- linux-2.6-spufs.orig/kernel/signal.c
> +++ linux-2.6-spufs/kernel/signal.c
> @@ -815,6 +815,7 @@ force_sig_info(int sig, struct siginfo *
>  
>  	return ret;
>  }
> +EXPORT_SYMBOL_GPL(force_sig_info);
>  
>  void
>  force_sig_specific(int sig, struct task_struct *t)

Perhaps export it from within a powerpc-specific C file (along with
suitable comment) to prevent people from generally relying upon the export?


  reply	other threads:[~2007-11-23  7:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-12  5:36 [RFC/PATCH] Export force_sig_info Jeremy Kerr
2007-11-23  7:41 ` Andrew Morton [this message]
2007-11-23 10:30   ` [Cbe-oss-dev] " Christoph Hellwig
2007-11-26  3:56   ` Jeremy Kerr

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=20071122234141.087743fa.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=cbe-oss-dev@ozlabs.org \
    --cc=jk@ozlabs.org \
    --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.