linux-kernel - Re: [Suggestion] PowerPC: kernel: cross compiling issue with allmodconfig

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <514D18A8.7080904@gmail.com>
Date:	Sat, 23 Mar 2013 10:51:20 +0800
From:	Chen Gang F T <chen.gang.flying.transformer@...il.com>
To:	Yoder Stuart-B08248 <B08248@...escale.com>
CC:	Michael Neuling <mikey@...ling.org>,
	Kumar Gala <galak@...nel.crashing.org>,
	Chen Gang <gang.chen@...anux.com>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	"sfr@...b.auug.org.au" <sfr@...b.auug.org.au>,
	"paulus@...ba.org" <paulus@...ba.org>,
	"matt@...abs.org" <matt@...abs.org>,
	"imunsie@....ibm.com" <imunsie@....ibm.com>,
	"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [Suggestion] PowerPC: kernel: cross compiling issue with allmodconfig

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/