From: SZALAY Attila <sasa@pheniscidae.tvnetwork.hu>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.5.54
Date: Fri, 3 Jan 2003 10:32:50 +0100 [thread overview]
Message-ID: <20030103093250.GC7661@sasa.home> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0301020745260.22868-100000@dragon.pdx.osdl.net>
Hi!
On 2003 Jan 02, Randy.Dunlap wrote:
>
> Yes, unfortunately this is a well-known problem.
> See kernel.bugzilla.org # 126 and # 164.
>
> You need to have CONFIG_INPUT=y, not =m.
Thank you, it's work.
But I have another problem.
drivers/message/i2o/i2o_lan.c:28: #error Please convert me to Documentation/DMA-mapping.txt
drivers/message/i2o/i2o_lan.c:119: parse error before `struct'
drivers/message/i2o/i2o_lan.c: In function 2o_lan_receive_post_reply':
drivers/message/i2o/i2o_lan.c:385: `run_i2o_post_buckets_task' undeclared (first use in this function)
drivers/message/i2o/i2o_lan.c:385: (Each undeclared identifier is reported only once
drivers/message/i2o/i2o_lan.c:385: for each function it appears in.)
drivers/message/i2o/i2o_lan.c: In function 2o_lan_register_device':
drivers/message/i2o/i2o_lan.c:1406: structure has no member named `list'
drivers/message/i2o/i2o_lan.c:1406: structure has no member named `list'
drivers/message/i2o/i2o_lan.c:1406: structure has no member named `list'
drivers/message/i2o/i2o_lan.c:1406: structure has no member named `list'
drivers/message/i2o/i2o_lan.c:1407: structure has no member named `sync'
make[4]: *** [drivers/message/i2o/i2o_lan.o] Error 1
make[3]: *** [drivers/message/i2o] Error 2
make[2]: *** [drivers/message] Error 2
make[1]: *** [drivers] Error 2
--
PGP ID 0x8D143771, /C5 95 43 F8 6F 19 E8 29 53 5E 96 61 05 63 42 D0
GPG ID ABA0E8B2, 45CF B559 8281 8091 8469 CACD DB71 AEFC ABA0 E8B2
Szeretem a Zsanit - SaSa
next prev parent reply other threads:[~2003-01-03 9:24 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 3:43 Linux v2.5.54 Linus Torvalds
2003-01-02 4:38 ` William Lee Irwin III
2003-01-02 10:43 ` Rusty Russell
2003-01-02 10:55 ` Andi Kleen
2003-01-02 11:13 ` William Lee Irwin III
2003-01-02 4:52 ` Linux v2.5.54 - OHCI-HCD build fails Murray J. Root
2003-01-02 5:00 ` Murray J. Root
2003-01-02 5:16 ` [PATCH] " Andres Salomon
2003-01-02 5:43 ` Murray J. Root
2003-01-02 6:10 ` Andres Salomon
2003-01-02 10:34 ` Linux v2.5.54 SZALAY Attila
2003-01-02 15:50 ` Randy.Dunlap
2003-01-02 15:56 ` Randy.Dunlap
2003-01-03 9:32 ` SZALAY Attila [this message]
2003-01-03 11:04 ` SZALAY Attila
2003-01-03 12:19 ` Alan Cox
2003-01-03 12:44 ` Christoph Hellwig
2003-01-03 16:13 ` Randy.Dunlap
2003-01-02 15:08 ` Adrian Bunk
2003-01-02 15:10 ` Christoph Hellwig
2003-01-02 17:18 ` Adrian Bunk
2003-01-02 17:31 ` Jaroslav Kysela
2003-01-02 13:26 ` Adam Belay
2003-01-03 0:08 ` [2.5.54] OOPS: unable to handle kernel paging request Steven Barnhart
2003-01-03 6:49 ` Paul Rolland
2003-01-02 17:49 ` Linux v2.5.54 Rudmer van Dijk
2003-01-02 23:48 ` [OOPS] Linux v2.5.54 Riva Framebuffer Udo A. Steinberg
2003-01-04 21:13 ` James Simmons
-- strict thread matches above, loose matches on Subject: below --
2003-01-02 14:42 Linux v2.5.54 Paolo Ciarrocchi
2003-01-04 10:20 ` Kasper Dupont
2003-01-04 11:47 Paolo Ciarrocchi
2003-01-04 12:27 ` Kasper Dupont
2003-01-04 14:06 Paolo Ciarrocchi
2003-01-04 14:19 ` Kasper Dupont
2003-01-04 17:10 Paolo Ciarrocchi
2003-01-04 18:14 Paolo Ciarrocchi
2003-01-04 22:14 ` Kasper Dupont
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=20030103093250.GC7661@sasa.home \
--to=sasa@pheniscidae.tvnetwork.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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