public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	David Miller <davem@davemloft.net>
Subject: Re: linux-next: build failure after merge final merge
Date: Tue, 16 Feb 2010 10:03:29 -0700	[thread overview]
Message-ID: <201002161003.29713.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <20100216183650.e82c0f8e.sfr@canb.auug.org.au>

On Tuesday 16 February 2010 12:36:50 am Stephen Rothwell wrote:
> After merging, today's linux-next build (sparc64 defconfig) failed like
> this:
> 
> arch/sparc/kernel/pci.c: In function 'pci_cfg_fake_ranges':
> arch/sparc/kernel/pci.c:404: error: 'struct pci_bus' has no member named 'resource'

Huh.  I built sparc64 defconfig (and alpha, arm, i686, ia64, mips,
powerpc, sh, and sparc) in Jesse's linux-next branch, but obviously
that's not doing the right thing for some reason.

> OK, I just checked the build results for last night
> (http://kisskb.ellerman.id.au/kisskb/head/2579/) and there are quite a few
> more (alpha, some arm, parisc and more ...) ... please fix them up as
> well.  Try something like:
> 
> git grep -l -w resource $(git grep -l -w 'struct pci_bus')
> 
> for a starting list of files to check.

Thanks for the specifics about all the failures.  That will help
me a lot.  And thanks for the git grep magic.  I've clearly been
missing out on a very useful tool.

Bjorn

  parent reply	other threads:[~2010-02-16 17:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-16  7:36 linux-next: build failure after merge final merge Stephen Rothwell
2010-02-16 16:36 ` Jesse Barnes
2010-02-16 17:05   ` Bjorn Helgaas
2010-02-16 17:03 ` Bjorn Helgaas [this message]
2010-02-16 17:41   ` Bjorn Helgaas
2010-02-16 23:09     ` 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=201002161003.29713.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas@hp.com \
    --cc=davem@davemloft.net \
    --cc=jbarnes@virtuousgeek.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