From: Vitaly Wool <vwool@ru.mvista.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
oprofile-list@lists.sourceforge.net
Subject: Re: [1/2] build failure for E500 CPUs w/ CONFIG_OPROFLE=y
Date: Fri, 27 Oct 2006 00:26:29 +0400 [thread overview]
Message-ID: <1161894389.2820.14.camel@barja> (raw)
In-Reply-To: <4A3EAE00-3647-4B72-8CDF-ED6E0ADEC910@kernel.crashing.org>
Hello Kumar,
> This makes sense to me since we are just increasing kernel code size
> for code we would never use for an FSL_BOOKE part if we do it the
> other way. I dont think its that much more messy with the ifdef's.
Okay, if you're fine with this patch, is it possible that you include it
into your tree?
> If you want to do the other cleanup as well I've got no issue with
> that, but we really should NOT build in support for 7450 into a
> FSL_BOOKE kernel when reasonably avoidable.
That's fine with me.
As of the cleanups, well... looks to me some more patches will follow
soon, kinda bugfixing ones rather than cleanups first :)
Thanks,
Vitaly
next prev parent reply other threads:[~2006-10-26 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 6:43 [1/2] build failure for E500 CPUs w/ CONFIG_OPROFLE=y Vitaly Wool
2006-10-26 13:57 ` Kumar Gala
2006-10-26 20:26 ` Vitaly Wool [this message]
2006-10-26 20:32 ` Sergei Shtylyov
2006-10-27 20:03 ` Andy Fleming
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=1161894389.2820.14.camel@barja \
--to=vwool@ru.mvista.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=oprofile-list@lists.sourceforge.net \
/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).