Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754164AbWKGQT5 (ORCPT ); Tue, 7 Nov 2006 11:19:57 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754205AbWKGQT5 (ORCPT ); Tue, 7 Nov 2006 11:19:57 -0500 Received: from mx.pathscale.com ([64.160.42.68]:4791 "EHLO mx.pathscale.com") by vger.kernel.org with ESMTP id S1754164AbWKGQT4 (ORCPT ); Tue, 7 Nov 2006 11:19:56 -0500 Message-ID: <4550B22C.1060307@serpentine.com> Date: Tue, 07 Nov 2006 08:19:56 -0800 From: "Bryan O'Sullivan" User-Agent: Thunderbird 1.5.0.7 (X11/20061008) MIME-Version: 1.0 To: "Eric W. Biederman" Cc: Adrian Bunk , Linux Kernel Mailing List Subject: Re: 2.6.19-rc4: known unfixed regressions (v3) References: <20061105064801.GV13381@stusta.de> <20061107042214.GC8099@stusta.de> <45501730.8020802@serpentine.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 667 Lines: 16 Eric W. Biederman wrote: > How comes the driver fixes in the context of my patches? The fix is simple enough, it's just not as clean as I'd like. I have to pull apart the contents of the ht_irq_msg that the new update hook is getting passed, in order to get the vector out, so that I can reprogram the offending chip register after I've done the config space writes. It's a pretty roundabout way to do the job.