From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [Bug 767] New: in ieee1394 file iso.c fails to compile
Date: Mon, 02 Jun 2003 16:35:40 -0700 [thread overview]
Message-ID: <209840000.1054596940@[10.10.2.4]> (raw)
Summary: in ieee1394 file iso.c fails to compile
Kernel Version: 2.5.70
Status: NEW
Severity: normal
Owner: bcollins@debian.org
Submitter: donaldlf@i-55.com
Distribution:redhat
Hardware Environment:Alpha PC164LX
Software Environment:Rawhide
Problem Description:
file fails to compile (as module embedded untested)
drivers/ieee1394/iso.c: In function `hpsb_iso_xmit_sync':
drivers/ieee1394/iso.c:355: arithmetic on pointer to an incomplete type
drivers/ieee1394/iso.c:355: warning: implicit declaration of function
`set_current_state'
drivers/ieee1394/iso.c:355: `TASK_INTERRUPTIBLE' undeclared (first use in this
function)
drivers/ieee1394/iso.c:355: (Each undeclared identifier is reported only once
drivers/ieee1394/iso.c:355: for each function it appears in.)
drivers/ieee1394/iso.c:355: warning: implicit declaration of function
`signal_pending'
drivers/ieee1394/iso.c:355: arithmetic on pointer to an incomplete type
drivers/ieee1394/iso.c:355: warning: implicit declaration of function `schedule'
drivers/ieee1394/iso.c:355: arithmetic on pointer to an incomplete type
drivers/ieee1394/iso.c:355: dereferencing pointer to incomplete type
drivers/ieee1394/iso.c:355: `TASK_RUNNING' undeclared (first use in this function)
drivers/ieee1394/iso.c: In function `hpsb_iso_wake':
drivers/ieee1394/iso.c:431: `TASK_INTERRUPTIBLE' undeclared (first use in this
function)
make[2]: *** [drivers/ieee1394/iso.o] Error 1
make[1]: *** [drivers/ieee1394] Error 2
make: *** [drivers] Error 2
Steps to reproduce:
Select ieee1394 as an module and activate all items lower in the configuration
tree as an module
Solution
Add the line
# include <linux/sched.h>
between the following lines (line number 11)
# include <linux/slab.h>
# include "iso.h"
reply other threads:[~2003-06-02 23:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='209840000.1054596940@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--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
all inboxes | Powered by JetHome®