From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jean Delvare Subject: Re: [i2c] [PATCH] update module-init-tools to support the i2c subsystem Date: Sun, 13 Jan 2008 16:35:43 +0100 Message-ID: <20080113163543.16e3d26b@hyperion.delvare> References: <9e4733910712171839h214e0bc3q179266c86e5987b1@mail.gmail.com> <20080113152735.5dca46a1@hyperion.delvare> <9e4733910801130714m1be16826jf240171972324d16@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <9e4733910801130714m1be16826jf240171972324d16@mail.gmail.com> Sender: linux-kernel-owner@vger.kernel.org To: Jon Smirl Cc: i2c@lm-sensors.org, linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org List-Id: linux-i2c@vger.kernel.org On Sun, 13 Jan 2008 10:14:14 -0500, Jon Smirl wrote: > On 1/13/08, Jean Delvare wrote: > > On Mon, 17 Dec 2007 21:39:37 -0500, Jon Smirl wrote: > > > Follow on to: "Series to add device tree naming to i2c" > > > Teach module-init-tools about the i2c subsystem. > > > > Can you please explain what this patch does and why it is needed? > > It generates the entries needed for the user space module tools to > work with the aliases. For example modprobe/depmod. It is a standard > part of the kernel module system. What entries, where? What can you do after applying your patch that you couldn't do before? I'm asking because automatic i2c driver loading works just fine for me without patching user-space. So I don't get why your want to change anything. -- Jean Delvare