From: Andreas Henriksson <andreas@fjortis.info>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOPS in read_cd... what to do?
Date: Tue, 28 Jan 2003 20:52:26 +0100 [thread overview]
Message-ID: <20030128195226.GA27417@foo> (raw)
In-Reply-To: <1043779710.24849.8.camel@irongate.swansea.linux.org.uk>
Hi..
It didn't help. :(
Though I had to change it some to get it to compile... hopefully I
didn't screw up. (I did this to avoid "invalid operators to binary +")
#define virt_addr(addr) *(volatile unsigned char *) __io_virt(addr)
and changed the isa_...(foo+bar); to isa_...(virt_addr(foo+bar));
The oops looks about the same.. so I guess the patch didn't do any
difference (even if it might be needed in the long run)...
Any more ideas? ;)
-- Andreas Henriksson
next prev parent reply other threads:[~2003-01-28 19:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 14:43 OOPS in read_cd... what to do? Mauricio Martinez
2003-01-27 16:23 ` Brian Gerst
2003-01-28 12:51 ` Andreas Henriksson
2003-01-28 18:48 ` Alan Cox
2003-01-28 19:52 ` Andreas Henriksson [this message]
2003-01-29 4:07 ` Cabletron E2100 (e2100.c) Oops Andreas Henriksson
2003-01-29 21:25 ` OOPS in read_cd... what to do? Faik Uygur
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=20030128195226.GA27417@foo \
--to=andreas@fjortis.info \
--cc=alan@lxorguk.ukuu.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.