linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: "Kay Sievers" <kay.sievers@vrfy.org>
Cc: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
	linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
	i2c@lm-sensors.org
Subject: Re: [i2c] [PATCH] update module-init-tools to support the i2c subsystem
Date: Mon, 14 Jan 2008 20:46:25 +0100	[thread overview]
Message-ID: <20080114204625.07293dce@hyperion.delvare> (raw)
In-Reply-To: <3ae72650801141138t27666bcerd66e96f836d1ab2b@mail.gmail.com>

On Mon, 14 Jan 2008 20:38:28 +0100, Kay Sievers wrote:
> On Jan 14, 2008 6:50 PM, Jean Delvare <khali@linux-fr.org> wrote:
> > I am under the impression that modules.*map are the old way to get
> > automatic driver loading and aliases are the new way to do the same.
> > But maybe that's just me.
> 
> Right, nothing on recent systems is using the map files. This patch
> should not be needed.
> The plan is to deprecate the creation of these files in depmod.

OK, great. Thanks for the info, Kay!

-- 
Jean Delvare

      reply	other threads:[~2008-01-14 19:46 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
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 [this message]

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=20080114204625.07293dce@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=i2c@lm-sensors.org \
    --cc=kay.sievers@vrfy.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).