From: Sam Ravnborg <sam@ravnborg.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [scsi bug] spurious build failures in aic7xxx
Date: Sat, 2 Feb 2008 00:02:10 +0100 [thread overview]
Message-ID: <20080201230210.GA18006@uranus.ravnborg.org> (raw)
In-Reply-To: <20080201225056.GA18302@elte.hu>
On Fri, Feb 01, 2008 at 11:50:56PM +0100, Ingo Molnar wrote:
>
> i'm getting spurious build failures with latest -git:
>
> In file included from drivers/scsi/aic7xxx/aic7xxx_proc.c:44:
> drivers/scsi/aic7xxx/aic7xxx_inline.h: In function 'ahc_pause_bug_fix':
> drivers/scsi/aic7xxx/aic7xxx_inline.h:66: error: 'CCSCBCTL' undeclared (first use in this function)
> drivers/scsi/aic7xxx/aic7xxx_inline.h:66: error: (Each undeclared
> identifier is reported only once
> drivers/scsi/aic7xxx/aic7xxx_inline.h:66: error: for each function it
> appears in.)
> drivers/scsi/aic7xxx/aic7xxx_inline.h: In function 'ahc_update_residual':
>
> BUT, if i redo the build, it now builds. It's probably some generated
> file ordering problem?
Most likely:
93a38fa2dd83fcaf65b2327fff65e364472388f9 [SCSI] aic7xxx: fix firmware build
I will take a look during the weekend.
One day I get this Makefile fixed properly (I hope).
Sam
next prev parent reply other threads:[~2008-02-01 23:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 22:50 [scsi bug] spurious build failures in aic7xxx Ingo Molnar
2008-02-01 23:02 ` Sam Ravnborg [this message]
2008-02-02 13:59 ` Sam Ravnborg
2008-02-02 14:03 ` Ingo Molnar
2008-02-02 14:06 ` Ingo Molnar
2008-02-02 14:18 ` Ingo Molnar
2008-02-02 16:26 ` Sam Ravnborg
2008-02-02 17:10 ` Ingo Molnar
2008-02-03 4:54 ` [patch] scsi: fix " Ingo Molnar
2008-02-03 7:41 ` Sam Ravnborg
2008-02-03 19:23 ` James Bottomley
2008-02-03 20:05 ` Sam Ravnborg
2008-02-03 20:15 ` James Bottomley
2008-02-03 20:38 ` Sam Ravnborg
2008-02-03 20:48 ` James Bottomley
2008-02-04 7:33 ` Hannes Reinecke
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=20080201230210.GA18006@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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