From: David Woodhouse <dwmw2@infradead.org>
To: Andrew Morton <akpm@osdl.org>
Cc: arjan@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Debug shared irqs.
Date: Thu, 05 Jan 2006 10:39:58 +0000 [thread overview]
Message-ID: <1136457598.4158.175.camel@pmac.infradead.org> (raw)
In-Reply-To: <20060105021929.498f45ef.akpm@osdl.org>
On Thu, 2006-01-05 at 02:19 -0800, Andrew Morton wrote:
> This is going to cause me a ton of grief. How's about you put it in
> Fedora for a few weeks, get all the drivers debugged first ;)
I'd do that normally, but it's the wrong point in the cycle -- we're
getting ready for Fedora Core 5 at the moment; it's not the time to be
doing such things. We can apply the patch... but we'd have to turn the
config option off :)
What you're seeing is the whole point of the patch, surely? And it _is_
a config option -- people aren't forced to turn it on.
Would it help if we added a printk to make it more obvious what's
happening, which gives the naïve user the opportunity to turn off the
config option just to get things working again? Somethign along the
lines of "Faking irq %d due to CONFIG_DEBUG_SHIRQ. If your machine
crashes now, don't blame akpm"?
Out of interest, does your i810 patch fix the problem which was reported
in November by Eyal Lebedinsky ("2.6.14.2: repeated oops in i810 init")?
--
dwmw2
next prev parent reply other threads:[~2006-01-05 10:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 11:42 David Woodhouse
2006-01-05 10:19 ` Andrew Morton
2006-01-05 10:39 ` David Woodhouse [this message]
2006-01-05 11:08 ` Andrew Morton
2006-01-05 10:48 ` Arjan van de Ven
2006-01-05 13:49 ` [PATCH] reduce sizeof(percpu_data) and removes dependance against NR_CPUS Eric Dumazet
2006-01-05 14:00 ` Andrew Morton
2006-01-05 14:33 ` Eric Dumazet
2006-01-06 7:18 ` Jan Engelhardt
2006-01-06 7:27 ` Andrew Morton
2006-01-06 7:29 ` Eric Dumazet
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=1136457598.4158.175.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--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®