From: Anton Blanchard <anton@samba.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Michel D?nzer <michel@daenzer.net>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Weird interrupt problem
Date: Sat, 10 Aug 2002 18:45:28 +1000 [thread overview]
Message-ID: <20020810084528.GA5338@krispykreme> (raw)
In-Reply-To: <20020808120700.30639@192.168.4.1>
> It may be some kind of race within the openpic driver when we keep
> enabling/disabling the source in ack() and end(). I'm pretty sure
> we don't really need them, oh well...
Yeah I pulled that out of the ppc64 tree and I havent found a problem
yet. Maybe there was some buggy ppc32 hardware that required this?
Anton
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-08-10 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 23:05 Weird interrupt problem Michel Dänzer
2002-08-07 23:14 ` Michel Dänzer
2002-08-08 0:28 ` Kevin B. Hendricks
2002-08-08 11:04 ` Michel Dänzer
2002-08-08 12:07 ` Benjamin Herrenschmidt
2002-08-10 8:45 ` Anton Blanchard [this message]
2002-08-16 17:01 ` Michel Dänzer
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=20020810084528.GA5338@krispykreme \
--to=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=michel@daenzer.net \
/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;
as well as URLs for NNTP newsgroup(s).