From: Chen Gang F T <chen.gang.flying.transformer@gmail.com>
To: Yoder Stuart-B08248 <B08248@freescale.com>
Cc: "sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
Michael Neuling <mikey@neuling.org>,
"matt@ozlabs.org" <matt@ozlabs.org>,
Chen Gang <gang.chen@asianux.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"paulus@samba.org" <paulus@samba.org>,
"imunsie@au1.ibm.com" <imunsie@au1.ibm.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [Suggestion] PowerPC: kernel: cross compiling issue with allmodconfig
Date: Sat, 23 Mar 2013 10:51:20 +0800 [thread overview]
Message-ID: <514D18A8.7080904@gmail.com> (raw)
In-Reply-To: <9F6FE96B71CF29479FF1CDC8046E150358CDE5@039-SN1MPN1-002.039d.mgd.msft.net>
On 2013年03月23日 03:17, Yoder Stuart-B08248 wrote:
> allmodconfig is creating config combinations that don't
> happen in a normal build (at least currently)-- 64-bit build
> that enables EPAPR_PARAVIRT but not PPC_BOOK3E_64.
if it should not happen.
can we add dependency to let it will never happen in any config combinations ?
let allmodconfig can not create this config combinamtions:
"64-bit build that enables EPAPR_PARAVIRT but not PPC_BOOK3E_64".
thanks.
--
Chen Gang
Flying Transformer
next prev parent reply other threads:[~2013-03-23 2:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 2:50 [Suggestion] PowerPC: kernel: cross compiling issue with allmodconfig Chen Gang
2013-03-15 4:52 ` Michael Neuling
2013-03-15 5:14 ` Chen Gang
2013-03-21 5:55 ` Chen Gang
[not found] ` <514AC418.1070806@gmail.com>
2013-03-21 12:38 ` Benjamin Herrenschmidt
2013-03-22 6:46 ` Chen Gang
2013-03-21 23:21 ` Michael Neuling
2013-03-22 19:17 ` Yoder Stuart-B08248
2013-03-23 2:51 ` Chen Gang F T [this message]
2013-03-21 22:54 ` Michael Neuling
2013-03-22 6:55 ` Chen Gang
2013-03-25 0:03 ` Michael Neuling
2013-03-25 1:07 ` Chen Gang
2013-03-25 1:31 ` [PATCH] PowerPC:kernel: make additional room in exception vector area Chen Gang
2013-03-25 5:14 ` Stephen Rothwell
2013-03-25 5:38 ` Chen Gang
2013-03-25 6:07 ` Michael Neuling
2013-03-25 6:20 ` Stephen Rothwell
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=514D18A8.7080904@gmail.com \
--to=chen.gang.flying.transformer@gmail.com \
--cc=B08248@freescale.com \
--cc=gang.chen@asianux.com \
--cc=imunsie@au1.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matt@ozlabs.org \
--cc=mikey@neuling.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/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).