From: Scott James Remnant <scott@ubuntu.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>,
linux-input@atrey.karlin.mff.cuni.cz, vojtech@suse.cz
Subject: Re: Two module-init-
Date: Fri, 02 Dec 2005 09:01:14 +0000 [thread overview]
Message-ID: <1133514074.20712.0.camel@localhost.localdomain> (raw)
In-Reply-To: <1133482376.4094.11.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
On Fri, 2005-12-02 at 11:12 +1100, Rusty Russell wrote:
> On Wed, 2005-11-30 at 14:09 +0000, Scott James Remnant wrote:
> > Hi Rusty,
> >
> > Attached are two patches to module-init-tools from Ubuntu.
> >
> > The first (input_table_size) is a catch-up with 2.6.15, it's adding an
> > extra field to the input_device_id struct; m-u-t needs updating to be
> > able to read the modules correctly.
>
> Unfortunately, it's not that simple. Your patch will break previous
> kernels, which have a smaller structure. I've had the discussion years
> ago with the input people on using module aliases, and it's not entirely
> trivial. I will prepare another patch, however.
>
Are the modules.*map files intended to be deprecated entirely in favour
of aliases? The problem this patch fixed was that the parser couldn't
read the tables, so produced invalid output for the modules (ie. an
empty modules.inputmap).
Scott
--
Scott James Remnant
scott@ubuntu.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-12-02 9:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1133359773.2779.13.camel@localhost.localdomain>
2005-12-02 0:12 ` Two module-init- Rusty Russell
2005-12-02 9:01 ` Scott James Remnant [this message]
2005-12-02 23:59 ` Rusty Russell
2005-12-03 4:46 ` Kay Sievers
2005-12-03 4:19 ` Dmitry Torokhov
2005-12-03 4:28 ` Dmitry Torokhov
2005-12-04 10:24 ` Rusty Russell
2005-12-05 17:30 ` Richard Purdie
2005-12-05 21:47 ` Dmitry Torokhov
2005-12-06 4:39 ` Rusty Russell
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=1133514074.20712.0.camel@localhost.localdomain \
--to=scott@ubuntu.com \
--cc=greg@kroah.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=vojtech@suse.cz \
/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