Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261709AbVAaJJ3 (ORCPT ); Mon, 31 Jan 2005 04:09:29 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261641AbVAaJJ3 (ORCPT ); Mon, 31 Jan 2005 04:09:29 -0500 Received: from styx.suse.cz ([82.119.242.94]:8865 "EHLO mail.suse.cz") by vger.kernel.org with ESMTP id S261862AbVAaJJ0 (ORCPT ); Mon, 31 Jan 2005 04:09:26 -0500 Date: Mon, 31 Jan 2005 10:13:03 +0100 From: Vojtech Pavlik To: Dmitry Torokhov Cc: linux-input@atrey.karlin.mff.cuni.cz, LKML Subject: Re: [PATCH 0/16] New set of input patches Message-ID: <20050131091303.GA28018@ucw.cz> References: <200412290217.36282.dtor_core@ameritech.net> <20050127221623.GA2300@ucw.cz> <200501301835.19220.dtor_core@ameritech.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200501301835.19220.dtor_core@ameritech.net> User-Agent: Mutt/1.5.6i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1036 Lines: 24 On Sun, Jan 30, 2005 at 06:35:18PM -0500, Dmitry Torokhov wrote: > > You're right. I forgot that serio isn't anymore tied to the driver and > > can cease to exist on its own asynchronously. However, I'm still not > > sure whether it's worth it. We might as well simply drop the unregister > > call in i8042_open for AUX completely and forget about asynchronous > > unregisters and use normal refcounting. As far as grep knows, it's the > > only user. > > I am pretty sure I will need asynchronous unregister in some form when > I finish dynamic protocol switching in psmouse (those darned pass-through > ports!). Plus again, having these 2 methods will draw driver writers' > attention to the existence of this particular problem. OK. I'm convinced. -- Vojtech Pavlik SuSE Labs, SuSE CR - 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/