[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4718F918.8050904@garzik.org>
Date: Fri, 19 Oct 2007 14:36:08 -0400
From: Jeff Garzik <jeff@...zik.org>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
CC: LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 4/9] irq-remove: driver non-trivial
Eric W. Biederman wrote:
> [snip] Found issues and ran out of review bandwidth.
thanks for the comments! I'll work through these.
There are definitely plenty of open issues I haven't yet tackled in the
driver area, as you are seeing. As you noted, a lot of these are with
drivers doing weird things like calling their own interrupt function
with (-1, NULL) or (0, NULL), which triggers some magic "I'm polling"
behavior.
>> }
>> __out:
>> spin_unlock(&mts->lock);
>> +
>> + return IRQ_HANDLED;
>
> Missing parport code change, see below.
those two parport changes were bogus, and actually got fixed up in patch #9
-
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