[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070226.094747.59657430.davem@davemloft.net>
Date: Mon, 26 Feb 2007 09:47:47 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: ebiederm@...ssion.com
Cc: linux-kernel@...r.kernel.org
Subject: Re: MSI entry unlinked before arch_teardown_msi_irq().
From: ebiederm@...ssion.com (Eric W. Biederman)
Date: Sun, 25 Feb 2007 17:14:43 -0700
> David Miller <davem@...emloft.net> writes:
>
> > From: ebiederm@...ssion.com (Eric W. Biederman)
> > Date: Sun, 25 Feb 2007 02:08:07 -0700
> >
> >> If that isn't the issue holler and I will look into it a little more.
> >
> > Talking in code is always more effective :-)
> >
> > This patch fixes the OOPS I was talking about:
>
> Ok. That is clearly reasonable. Why do you need to traverse
> the list here? I just want to understand the requirements.
The real problem turned out to be my using get_irq_data() instead
of get_irq_msi() :-)
Sorry for the noise.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists