From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Borislav Petkov <petkovbb@googlemail.com>
Subject: Re: linux-next: ide tree build failure
Date: Mon, 8 Dec 2008 18:10:59 +0100 [thread overview]
Message-ID: <200812081810.59270.bzolnier@gmail.com> (raw)
In-Reply-To: <20081208131609.c6e0fd31.sfr@canb.auug.org.au>
On Monday 08 December 2008, Stephen Rothwell wrote:
> Hi Bart,
>
> Today's linux-next build (powerpc ppc64_defconfig) failed like this:
>
> drivers/built-in.o: In function `.ide_cd_do_request':
> ide-cd.c:(.text+0x11a97c): undefined reference to `.ide_cd_get_xferlen'
> drivers/built-in.o:(.toc1+0x83b8): undefined reference to `ide_cd_expiry'
I see, BLK_DEV_IDECD needs to select IDE_ATAPI now. I updated
ide-atapi-accomodate-transfer-length-calculation-for-ide-cd.patch
accordingly so ppc64_defconfing should build fine again.
Thanks,
Bart
next prev parent reply other threads:[~2008-12-08 17:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 2:16 linux-next: ide tree build failure Stephen Rothwell
2008-12-08 17:10 ` Bartlomiej Zolnierkiewicz [this message]
2008-12-08 17:49 ` Borislav Petkov
2008-12-09 0:12 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2009-06-15 1:34 Stephen Rothwell
2009-06-15 5:35 ` Borislav Petkov
2009-06-15 16:14 ` Bartlomiej Zolnierkiewicz
2009-02-06 3:35 Stephen Rothwell
2009-01-22 1:57 Stephen Rothwell
2009-01-22 13:22 ` Bartlomiej Zolnierkiewicz
2009-01-22 22:14 ` Stephen Rothwell
2008-08-26 4:06 Stephen Rothwell
2008-08-26 20:04 ` Bartlomiej Zolnierkiewicz
2008-08-12 1:18 Stephen Rothwell
2008-08-12 7:36 ` Borislav Petkov
2008-08-12 9:15 ` Bartlomiej Zolnierkiewicz
2008-07-24 3:17 Stephen Rothwell
2008-07-24 18:41 ` Bartlomiej Zolnierkiewicz
2008-06-30 5:28 Stephen Rothwell
2008-06-30 18:38 ` Bartlomiej Zolnierkiewicz
2008-07-01 0:28 ` 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=200812081810.59270.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-next@vger.kernel.org \
--cc=petkovbb@googlemail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.