linux-kernel - Re: linux-next: Tree for January 6 (MTD)

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: <496386DB.8090606@oracle.com>
Date:	Tue, 06 Jan 2009 08:29:15 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	David Woodhouse <dwmw2@...radead.org>,
	Korolev Alexey <akorolev@...radead.org>,
	Vasiliy Leonenko <vasiliy.leonenko@...il.com>
Subject: Re: linux-next: Tree for January 6 (MTD)

Stephen Rothwell wrote:
> Hi all,
> 
> This tree will not build a powerpc ppc4xx_defconfig due to a kvm problem.
> 
> Changes since 20090105:
> 
> New tree:
> 	squashfs
> 
> Undropped tree:
> 	usb
> 	staging
> 
> Dropped trees (temporarily):
> 	rr (build problem)
> 	semaphore-removal (due to unfixed conflicts against Linus' tree)
> 	cpu_alloc (build problem)
> 	audit (difficult conflicts)
> 
> 
> The mtd tree lost 3 conflicts.

drivers/built-in.o: In function `lpddr_probe':
(.text+0x95ddc): undefined reference to `lpddr_cmdset'

with
# CONFIG_MTD_LPDDR is not set
CONFIG_MTD_QINFO_PROBE=y

There appears to be too little control/coordination between those
two kconfig symbols.  Surely one of them (MTD_QINFO_PROBE) should
depend on the other (MTD_LPDDR).  And why even build 2 modules
when MTD_QINFO_PROBE is enabled?  Why not combine the code into
one module?


-- 
~Randy
--
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/