From: Ingo Molnar <mingo@elte.hu>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: "Barry K. Nathan" <barryn@pobox.com>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [patch, -rc5-mm3] lock validator: fix ns83820.c irq-flags part 3
Date: Sun, 4 Jun 2006 12:11:36 +0200 [thread overview]
Message-ID: <20060604101136.GA14693@elte.hu> (raw)
In-Reply-To: <1149415707.3109.96.camel@laptopd505.fenrus.org>
* Arjan van de Ven <arjan@linux.intel.com> wrote:
> On Sun, 2006-06-04 at 02:53 -0700, Barry K. Nathan wrote:
> > On 6/4/06, Arjan van de Ven <arjan@linux.intel.com> wrote:
> > > just the preempt the next email from Barry; while fixing this one I
> > > looked at the usage of the locks more and found another patch needed...
> > [snip]
> >
> > Nice try, but it didn't work. ~_^
> >
> > I was about to reply to the previous ns83820 patch with my dmesg, when
> > I saw this one. I applied this patch too, and like the previous patch,
> > it reports an instance of illegal lock usage. My dmesg follows.
> > --
>
> ok this is a real driver deadlock:
preexisting bug, right? So this fix should go into 2.6.16/17 too,
correct?
Ingo
next prev parent reply other threads:[~2006-06-04 10:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-04 8:30 [patch, -rc5-mm3] lock validator: fix ns83820.c irq-flags bug Ingo Molnar
2006-06-04 8:50 ` Keith Owens
2006-06-04 8:58 ` Ingo Molnar
[not found] ` <1149411525.3109.73.camel@laptopd505.fenrus.org>
2006-06-04 9:53 ` [patch, -rc5-mm3] lock validator: fix ns83820.c irq-flags bug part 2 Barry K. Nathan
2006-06-04 10:08 ` [patch, -rc5-mm3] lock validator: fix ns83820.c irq-flags part 3 Arjan van de Ven
2006-06-04 10:11 ` Ingo Molnar [this message]
2006-06-04 10:16 ` Arjan van de Ven
2006-06-04 10:46 ` Barry K. Nathan
2006-06-04 11:02 ` Ingo Molnar
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=20060604101136.GA14693@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=arjan@linux.intel.com \
--cc=barryn@pobox.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 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.