From: Dave Jones <davej@redhat.com>
To: Bob Gill <gillb4@telusplanet.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: drivers/ieee1394/sbp2.c:734: error: `host' undeclared (first use in this function) 2.6.3-bk3
Date: Sun, 22 Feb 2004 01:04:25 +0000 [thread overview]
Message-ID: <20040222010424.GA16018@redhat.com> (raw)
In-Reply-To: <1077399402.22141.86.camel@localhost.localdomain>
On Sat, Feb 21, 2004 at 02:36:43PM -0700, Bob Gill wrote:
> Hi. The whole error message is (when building 2.6.3-bk3):
> drivers/ieee1394/sbp2.c: In function `sbp2_alloc_device':
> drivers/ieee1394/sbp2.c:734: error: `host' undeclared (first use in this
> function)
> drivers/ieee1394/sbp2.c:734: error: (Each undeclared identifier is
> reported only once
> drivers/ieee1394/sbp2.c:734: error: for each function it appears in.)
> make[2]: *** [drivers/ieee1394/sbp2.o] Error 1
> make[1]: *** [drivers/ieee1394] Error 2
> make: *** [drivers] Error 2
I've no hardware to test this, but does this do the right thing for you ?
Dave
--- linux-2.6.3/drivers/ieee1394/sbp2.c~ 2004-02-22 00:54:51.000000000 +0000
+++ linux-2.6.3/drivers/ieee1394/sbp2.c 2004-02-22 00:55:11.000000000 +0000
@@ -727,7 +727,7 @@
#ifdef CONFIG_IEEE1394_SBP2_PHYS_DMA
/* Handle data movement if physical dma is not
* enabled/supportedon host controller */
- hpsb_register_addrspace(&sbp2_highlevel, host, &sbp2_physdma_ops,
+ hpsb_register_addrspace(&sbp2_highlevel, hi->host, &sbp2_physdma_ops,
0x0ULL, 0xfffffffcULL);
#endif
}
next prev parent reply other threads:[~2004-02-22 1:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-21 21:36 drivers/ieee1394/sbp2.c:734: error: `host' undeclared (first use in this function) 2.6.3-bk3 Bob Gill
2004-02-22 0:21 ` Ben Collins
2004-02-22 1:04 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-22 7:18 Bob Gill
2004-02-27 15:07 Brad Davidson
2004-02-27 16:21 ` Dave Jones
2004-02-27 20:57 Bob Gill
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=20040222010424.GA16018@redhat.com \
--to=davej@redhat.com \
--cc=gillb4@telusplanet.net \
--cc=linux-kernel@vger.kernel.org \
/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