linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Christoph Hellwig <hch@lst.de>
Cc: linuxppc-dev@ozlabs.org, cbe-oss-dev@ozlabs.org,
	Arnd Bergmann <arnd.bergmann@de.ibm.com>
Subject: Re: [Cbe-oss-dev] [PATCH 4/5] powerpc: export symbols for page size selection
Date: Tue, 11 Apr 2006 11:21:56 +1000	[thread overview]
Message-ID: <1144718517.19353.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20060407152813.GA382@lst.de>

On Fri, 2006-04-07 at 17:28 +0200, Christoph Hellwig wrote:
> On Fri, Apr 07, 2006 at 12:00:04AM +0200, arnd@arndb.de wrote:
> > We need access to some symbols in powerpc memory management
> > from spufs in order to create proper SLB entries.
> 
> One more reason to disallow modular spufs..

Why ? It's not problem as long as they are exported GPL only ...

Ben.

  parent reply	other threads:[~2006-04-11  1:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-07 15:01 [PATCH 0/5] cell: recent bug fixes arnd
2006-04-06 22:00 ` [PATCH 1/5] spufs: Disable local interrupts for SPE hash_page calls arnd
2006-04-06 22:00 ` [PATCH 2/5] powerpc: fix 64k pages on non-hypervisor arnd
2006-04-06 22:00 ` [PATCH 3/5] spufs: set up correct SLB entries for 64k pages arnd
2006-04-06 22:00 ` [PATCH 4/5] powerpc: export symbols for page size selection arnd
2006-04-07 15:28   ` Christoph Hellwig
2006-04-07 15:42     ` Olof Johansson
2006-04-07 15:54       ` [Cbe-oss-dev] " Geoff Levand
2006-04-07 16:03       ` Arnd Bergmann
2006-04-07 16:20         ` Olof Johansson
2006-04-07 16:49           ` Arnd Bergmann
2006-04-11  1:21     ` Benjamin Herrenschmidt [this message]
2006-04-06 22:00 ` [PATCH 5/5] cell: enable CPU_FTR_CI_LARGE_PAGE arnd

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=1144718517.19353.7.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=arnd.bergmann@de.ibm.com \
    --cc=cbe-oss-dev@ozlabs.org \
    --cc=hch@lst.de \
    --cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).