All of lore.kernel.org
 help / color / mirror / Atom feed
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 16:50:59 -0400	[thread overview]
Message-ID: <47F694B3.5000002@garzik.org> (raw)
In-Reply-To: <20080404133931.482d8614.randy.dunlap@oracle.com>

Randy Dunlap wrote:
> On Fri, 04 Apr 2008 16:23:53 -0400 Jeff Garzik wrote:
> 
>> Randy Dunlap wrote:
>>> Jeff Garzik wrote:
>>>> 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?
>>> I'm just trying to build linux-next with or without today's "libata fixes".
>>> ATA with CONFIG_PCI=n still has build errors, as reported above.
>> OK, that's expected.
> 
> Uh, that's not good.  What does it mean?
> 
> (a) linux-next is not pulling the correct branch of your git tree
> or
> (b) linux-next just won't work with libata
> or
> (c) we have too many trees in the forest
> or
> something else?  (if so, what?)

It means you are inside the window between unfixed linux-next and 
tomorrow's fixed linux-next, and that you attempted to seek the proper 
fix in the wrong location.

So the next time linux-next pulls from libata, it should be fixed.

Or, if you don't want to wait, you should get the fix from the location 
noted (#upstream branch), because the fix was not among those sent to 
Linus yesterday.

	Jeff



      reply	other threads:[~2008-04-04 20:51 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
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 [this message]

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=47F694B3.5000002@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.