linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Korolev Alexey <akorolev@infradead.org>,
	Vasiliy Leonenko <vasiliy.leonenko@gmail.com>
Subject: Re: linux-next: Tree for January 6 (MTD)
Date: Tue, 06 Jan 2009 08:29:15 -0800	[thread overview]
Message-ID: <496386DB.8090606@oracle.com> (raw)
In-Reply-To: <20090106182311.525e4b14.sfr@canb.auug.org.au>

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

  reply	other threads:[~2009-01-06 16:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06  7:23 linux-next: Tree for January 6 Stephen Rothwell
2009-01-06 16:29 ` Randy Dunlap [this message]
2009-01-06 17:36   ` linux-next: Tree for January 6 (MTD) Alexey Korolev
2009-01-06 21:16     ` Randy Dunlap
2009-01-09 21:48     ` Randy Dunlap
2009-01-06 21:23 ` linux-next: Tree for January 6 (wimax errs) Randy Dunlap
2009-01-06 21:50   ` Iñaky Pérez-González
2009-01-07  8:09     ` Inaky Perez-Gonzalez
2009-01-07  0:25 ` linux-next: Tree for January 6 (staging/altpciehdma) Randy Dunlap
2009-01-07  0:26 ` linux-next: Tree for January 6 (staging/comedi) Randy Dunlap
2009-01-07  0:35 ` linux-next: Tree for January 6 (staging/meilhaus) Randy Dunlap
2009-01-07  0:37 ` linux-next: Tree for January 6 (staging/android) Randy Dunlap
2009-01-07  0:39 ` linux-next: Tree for January 6 (staging/android #2) Randy Dunlap
2009-01-07  0:53   ` Greg KH

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=496386DB.8090606@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akorolev@infradead.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=vasiliy.leonenko@gmail.com \
    /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).