From: Michael Ellerman <mpe@ellerman.id.au>
To: Paul Gortmaker <paul.gortmaker@windriver.com>,
<linux-kernel@vger.kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [1/3] powerpc: make cell/spu_base.c explicitly non-modular
Date: Mon, 11 Apr 2016 22:35:05 +1000 (AEST) [thread overview]
Message-ID: <3qk8fK6kfzz9t3g@ozlabs.org> (raw)
In-Reply-To: <1459116497-19991-2-git-send-email-paul.gortmaker@windriver.com>
On Sun, 2016-27-03 at 22:08:15 UTC, Paul Gortmaker wrote:
> The Kconfig currently controlling compilation of this code is:
>
> arch/powerpc/platforms/cell/Kconfig:config SPU_BASE
> arch/powerpc/platforms/cell/Kconfig: bool
>
> ...meaning that it currently is not being built as a module by anyone.
>
> Lets remove the modular code that is essentially orphaned, so that
> when reading the driver there is no doubt it is builtin-only.
...
>
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/8038665fb54f1e54785c63be11
cheers
next prev parent reply other threads:[~2016-04-11 12:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-27 22:08 [PATCH 0/3] powerpc: remove unused modular code from non-modular drivers Paul Gortmaker
2016-03-27 22:08 ` Paul Gortmaker
2016-03-27 22:08 ` [PATCH 1/3] powerpc: make cell/spu_base.c explicitly non-modular Paul Gortmaker
2016-04-11 12:35 ` Michael Ellerman [this message]
2016-03-27 22:08 ` [PATCH 2/3] powerpc: make kernel/nvram_64.c " Paul Gortmaker
2016-03-28 14:22 ` Nathan Fontenot
2016-04-11 12:35 ` [2/3] " Michael Ellerman
2016-03-27 22:08 ` [PATCH 3/3] drivers/cpufreq: make ppc_cbe_cpufreq_pmi driver " Paul Gortmaker
2016-03-27 22:08 ` Paul Gortmaker
2016-03-28 2:33 ` Viresh Kumar
2016-04-11 12:35 ` [3/3] " Michael Ellerman
2016-04-11 12:35 ` Michael Ellerman
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=3qk8fK6kfzz9t3g@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paul.gortmaker@windriver.com \
--cc=paulus@samba.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.