From: Jeremy Kerr <jk@ozlabs.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, cbe-oss-dev@ozlabs.org
Subject: Re: [RFC/PATCH] Export force_sig_info
Date: Mon, 26 Nov 2007 14:56:51 +1100 [thread overview]
Message-ID: <200711261456.53683.jk@ozlabs.org> (raw)
In-Reply-To: <20071122234141.087743fa.akpm@linux-foundation.org>
Hi Andrew,
> Perhaps export it from within a powerpc-specific C file (along with
> suitable comment) to prevent people from generally relying upon the
> export?
Even better, I'll export it from a Cell-specific C file. I'll follow
this up in my own spufs series for .25.
Cheers,
Jeremy
prev parent reply other threads:[~2007-11-26 3:57 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
2007-11-23 10:30 ` [Cbe-oss-dev] " Christoph Hellwig
2007-11-26 3:56 ` Jeremy Kerr [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=200711261456.53683.jk@ozlabs.org \
--to=jk@ozlabs.org \
--cc=akpm@linux-foundation.org \
--cc=cbe-oss-dev@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.