From: Jeff Garzik <jeff@garzik.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org,
Haavard Skinnemoen <hskinnemoen@atmel.com>,
linux-ide@vger.kernel.org
Subject: Re: linux-next: libata/avr32 build failure
Date: Fri, 04 Apr 2008 14:45:58 -0400 [thread overview]
Message-ID: <47F67766.6030903@garzik.org> (raw)
In-Reply-To: <20080404095408.88a92c7c.randy.dunlap@oracle.com>
Randy Dunlap wrote:
> On Fri, 04 Apr 2008 04:06:56 -0400 Jeff Garzik wrote:
>
>> Stephen Rothwell wrote:
>>> Hi Jeff,
>>>
>>> For a while the linux-next build for avr32 defconfig (and others) has
>>> been failing like this:
>>>
>>> drivers/ata/libata-core.c:127: error: 'ata_pci_default_filter' undeclared here (not in a function)
>>>
>>> It seems to be because the declaration of ata_pci_default_filter is
>>> protected by CONFIG_PCI but the usage above is protected by CONFIG_ATA
>>> only.
>>>
>>> Also reported by Randy Dunlap (on March 26) and Haavard Skinnemoen (on
>>> March 29).
>> fixed being pushed right now (patch from Tejun fixed it)
>
> Some fixes other than what was in today's (April 04)
> [git patches] libata fixes?
>
> I hope there is more. I don't see how that fixes this error.
> Nor does gcc see how, after I apply that patch.
It wasn't sent in #upstream-fixes, it was applied to #upstream...
Is that where you are looking?
Jeff
next prev parent reply other threads:[~2008-04-04 18:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 6:10 linux-next: libata/avr32 build failure Stephen Rothwell
2008-04-04 6:14 ` Stephen Rothwell
2008-04-04 8:06 ` Jeff Garzik
2008-04-04 10:35 ` Stephen Rothwell
2008-04-04 16:54 ` Randy Dunlap
2008-04-04 18:45 ` Jeff Garzik [this message]
2008-04-04 18:54 ` Randy Dunlap
2008-04-04 20:23 ` Jeff Garzik
2008-04-04 20:39 ` Randy Dunlap
2008-04-04 20:50 ` Jeff Garzik
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=47F67766.6030903@garzik.org \
--to=jeff@garzik.org \
--cc=hskinnemoen@atmel.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.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.