Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261392AbVEIX13 (ORCPT ); Mon, 9 May 2005 19:27:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261377AbVEIXX7 (ORCPT ); Mon, 9 May 2005 19:23:59 -0400 Received: from lyle.provo.novell.com ([137.65.81.174]:26753 "EHLO lyle.provo.novell.com") by vger.kernel.org with ESMTP id S261392AbVEIXWF (ORCPT ); Mon, 9 May 2005 19:22:05 -0400 Date: Mon, 9 May 2005 16:22:07 -0700 From: Greg KH To: Per Liden Cc: linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org Subject: Re: [ANNOUNCE] hotplug-ng 002 release Message-ID: <20050509232207.GB24238@suse.de> References: <20050506212227.GA24066@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1006 Lines: 31 On Mon, May 09, 2005 at 12:52:02AM +0200, Per Liden wrote: > On Fri, 6 May 2005, Greg KH wrote: > > [...] > > Now, with the 2.6.12-rc3 kernel, and a patch for module-init-tools, the > > USB hotplug program can be written with a simple one line shell script: > > modprobe $MODALIAS > > Nice, but why not just convert all this to a call to > request_module($MODALIAS)? Seems to me like the natural thing to do. Because that's not the only thing that the hotplug event causes to happen. It's easier to have userspace decide what to do with this instead. > [...] > > Oh, and the upstream module-init-tools maintainer needs to accept that > > patch one of these days... > > Where can this patch be found? Just sent it to this same thread. thanks, greg k-h - 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/