From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Jean Delvare" <khali@linux-fr.org>
Cc: linuxppc-dev@ozlabs.org, i2c@lm-sensors.org,
linux-kernel@vger.kernel.org
Subject: Re: [i2c] [PATCH] update module-init-tools to support the i2c subsystem
Date: Sun, 13 Jan 2008 11:26:07 -0500 [thread overview]
Message-ID: <9e4733910801130826l799e4897pe7380ccb973b5fd0@mail.gmail.com> (raw)
In-Reply-To: <20080113163543.16e3d26b@hyperion.delvare>
On 1/13/08, Jean Delvare <khali@linux-fr.org> wrote:
> On Sun, 13 Jan 2008 10:14:14 -0500, Jon Smirl wrote:
> > On 1/13/08, Jean Delvare <khali@linux-fr.org> 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?
The drivers you are testing with don't depend on other drivers.
> 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
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2008-01-13 16:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 2:39 [PATCH] update module-init-tools to support the i2c subsystem Jon Smirl
2008-01-13 14:27 ` [i2c] " Jean Delvare
2008-01-13 15:14 ` Jon Smirl
2008-01-13 15:35 ` Jean Delvare
2008-01-13 16:26 ` Jon Smirl [this message]
2008-01-13 17:43 ` Jean Delvare
2008-01-13 18:04 ` Jon Smirl
2008-01-14 10:57 ` Geert Uytterhoeven
2008-01-14 14:25 ` Jon Smirl
2008-01-14 16:38 ` Jean Delvare
2008-01-14 17:08 ` Geert Uytterhoeven
2008-01-14 17:50 ` Jean Delvare
2008-01-14 19:38 ` Kay Sievers
2008-01-14 19:46 ` Jean Delvare
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9e4733910801130826l799e4897pe7380ccb973b5fd0@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=i2c@lm-sensors.org \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).