From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: benh@kernel.crashing.org
Cc: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org, bzolnier@gmail.com
Subject: Re: linux-next: Tree for October 24 - powerpc - build failure with !CONFIG_BLK_DEV_IDEDMA_PMAC
Date: Sat, 25 Oct 2008 02:39:31 +0400 [thread overview]
Message-ID: <49024EA3.1080404@ru.mvista.com> (raw)
In-Reply-To: <1224886062.7654.464.camel@pasglop>
Hello.
Benjamin Herrenschmidt wrote:
>>> next-20081024 randconfig build fails on the powerpc, with
>>>
>>> drivers/ide/pmac.c: In function 'pmac_ide_set_pio_mode':
>>> drivers/ide/pmac.c:527: error: implicit declaration of function 'kauai_lookup_timing'
>>> drivers/ide/pmac.c:527: error: 'shasta_pio_timings' undeclared (first use in this function)
>>> drivers/ide/pmac.c:527: error: (Each undeclared identifier is reported only once
>>> drivers/ide/pmac.c:527: error: for each function it appears in.)
>>> drivers/ide/pmac.c:534: error: 'kauai_pio_timings' undeclared (first use in this function)
>>> drivers/ide/pmac.c: In function 'pmac_ide_do_resume':
>>> drivers/ide/pmac.c:914: error: 'IDE_WAKEUP_DELAY' undeclared (first use in this function)
>>> drivers/ide/pmac.c: At top level:
>>> drivers/ide/pmac.c:1007: error: 'pmac_ide_init_dma' undeclared here (not in a function)
>>> drivers/ide/pmac.c: In function 'pmac_ide_setup_device':
>>> drivers/ide/pmac.c:1107: error: 'IDE_WAKEUP_DELAY' undeclared (first use in this function)
>>> drivers/ide/pmac.c: In function 'pmac_ide_macio_attach':
>>> drivers/ide/pmac.c:1209: error: 'pmac_ide_hwif_t' has no member named 'dma_regs'
>>> drivers/ide/pmac.c:1210: error: 'pmac_ide_hwif_t' has no member named 'dma_regs'
>>> make[2]: *** [drivers/ide/pmac.o] Error 1
>>>
>>>
>> Hm, looks like this configuration was never buildable -- #ifdef's are
>> missing and wrongly placed. CCing Ben Herrenschmidt...
>>
>
> What configuration ?
>
See the subject.
> Ben.
MBR, Sergei
next prev parent reply other threads:[~2008-10-24 22:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 6:19 linux-next: Tree for October 24 Stephen Rothwell
2008-10-24 11:38 ` linux-next: Tree for October 24 - powerpc - build failure with !CONFIG_BLK_DEV_IDEDMA_PMAC Kamalesh Babulal
2008-10-24 12:15 ` Sergei Shtylyov
2008-10-24 22:07 ` Benjamin Herrenschmidt
2008-10-24 22:39 ` Sergei Shtylyov [this message]
2008-10-24 23:10 ` Benjamin Herrenschmidt
2008-10-25 13:19 ` Bartlomiej Zolnierkiewicz
2008-10-25 18:57 ` Sergei Shtylyov
2008-10-25 19:35 ` Bartlomiej Zolnierkiewicz
2008-12-07 14:27 ` Bartlomiej Zolnierkiewicz
2008-12-08 9:05 ` Kamalesh Babulal
2008-12-08 21:53 ` Benjamin Herrenschmidt
2008-12-08 21:54 ` Benjamin Herrenschmidt
2008-10-26 0:16 ` linux-next: Tree for October 24 (ACPI) Randy Dunlap
2008-10-26 10:59 ` Rafael J. Wysocki
2008-10-26 0:18 ` linux-next: Tree for October 24 (usbip) Randy Dunlap
2008-10-26 5:41 ` Greg KH
2008-10-26 0:21 ` linux-next: Tree for October 24 (ieee80211) Randy Dunlap
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=49024EA3.1080404@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=benh@kernel.crashing.org \
--cc=bzolnier@gmail.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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).