Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753681AbWKDThY (ORCPT ); Sat, 4 Nov 2006 14:37:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753683AbWKDThY (ORCPT ); Sat, 4 Nov 2006 14:37:24 -0500 Received: from nf-out-0910.google.com ([64.233.182.190]:19990 "EHLO nf-out-0910.google.com") by vger.kernel.org with ESMTP id S1753652AbWKDThX (ORCPT ); Sat, 4 Nov 2006 14:37:23 -0500 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=OBUrP0CrwERqbAqdTFPCKWGpItcUKquuyYfxqlg6E1CAXt0zUq6Lpln4N5fmFccU583qv6/d0RKhFz7ixETO2RVJFMIy+JAd63gT12m6n/4l328OkELavnScn9q1J5gAi8HI9WPwI8L/fHUv8ebtCsw95CAIpQ84XTEH+hmavKo= Message-ID: <86802c440611041137t74d84e7at3850fc8a10a314cb@mail.gmail.com> Date: Sat, 4 Nov 2006 11:37:22 -0800 From: "Yinghai Lu" To: "Eric W. Biederman" Subject: Re: [RFC][PATCH 2/2] htirq: Allow buggy drivers of buggy hardware to write the registers. Cc: "Bryan O'Sullivan" , olson@pathscale.com, linux-kernel@vger.kernel.org In-Reply-To: <200611032146.kA3LkUe9031799@ebiederm.dsl.xmission.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <454A7B0F.7060701@pathscale.com> <454B7B70.9060104@pathscale.com> <454B880A.1010802@pathscale.com> <454B8E19.90300@pathscale.com> <200611032146.kA3LkUe9031799@ebiederm.dsl.xmission.com> X-Google-Sender-Auth: a5a9377907b6a3cd Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 333 Lines: 9 why not create one standard update function. and use that us default for cfg->update YH - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/