From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Cc: Alexander Graf <agraf@suse.de>
Subject: Re: [PATCH] powerpc: Don't export cvt_fd & _df when CONFIG_PPC_FPU is not set
Date: Mon, 31 May 2010 12:00:31 +1000 [thread overview]
Message-ID: <1275271231.1931.547.camel@pasglop> (raw)
In-Reply-To: <1275270628.1931.540.camel@pasglop>
On Mon, 2010-05-31 at 11:50 +1000, Benjamin Herrenschmidt wrote:
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> ---
> arch/powerpc/kernel/ppc_ksyms.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Alex, this is just a temporary fix to remove the build breakage for 40x
etc... but please, update KVM to just build-in its own.
Don't we have .o's that are always built into modules nowadays ?
Cheers,
Ben.
next prev parent reply other threads:[~2010-05-31 2:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 1:50 [PATCH] powerpc: Don't export cvt_fd & _df when CONFIG_PPC_FPU is not set Benjamin Herrenschmidt
2010-05-31 2:00 ` Benjamin Herrenschmidt [this message]
2010-05-31 9:33 ` Alexander Graf
2010-05-31 9:52 ` Andreas Schwab
2010-05-31 15:52 ` Alexander Graf
[not found] ` <4C03DB3D.7090007__38063.9078132392$1275321190$gmane$org@suse.de>
2010-05-31 18:06 ` Andreas Schwab
2010-05-31 18:52 ` Alexander Graf
2010-06-01 9:31 ` Benjamin Herrenschmidt
[not found] ` <1275384716.1931.711.camel__10281.3212587082$1275384770$gmane$org@pasglop>
2010-06-01 9:36 ` Andreas Schwab
2010-06-01 9:46 ` Benjamin Herrenschmidt
[not found] ` <1275385607.1931.712.camel__30394.2679115154$1275385651$gmane$org@pasglop>
2010-06-01 15:58 ` [PATCH] macio: don't dereference pointer before null check Andreas Schwab
[not found] ` <m3mxvfrt5n.fsf__49359.5060579993$1275385036$gmane$org@hase.home>
2010-06-01 18:58 ` [PATCH] powerpc: Don't export cvt_fd & _df when CONFIG_PPC_FPU is not set Andreas Schwab
2010-06-02 7:11 ` Benjamin Herrenschmidt
2010-05-31 10:24 ` Benjamin Herrenschmidt
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=1275271231.1931.547.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=agraf@suse.de \
--cc=linuxppc-dev@lists.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).