public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Scott James Remnant <scott@ubuntu.com>
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 11:12:56 +1100	[thread overview]
Message-ID: <1133482376.4094.11.camel@localhost.localdomain> (raw)
In-Reply-To: <1133359773.2779.13.camel@localhost.localdomain>

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.

Hi Scott,

	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.

Meanwhile, as noone seems to use swbit in struct input_device_id,
perhaps we can remove it for 2.6.15?

> The second (use_blacklist) adds a "-b" flag to modprobe that performs
> blacklist checking on those modules listed on the command line, it's
> handy for use when calling modprobe from udev for those subsystems
> without MODALIAS yet (input, ccw, etc.)

Hmm, well, the answer to that is the same as above.  ccw should have
support now, so it's just input we're missing I think.

Rusty.
-- 
A bad analogy is like a leaky screwdriver -- Richard Braakman


       reply	other threads:[~2005-12-02  0:12 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 ` Rusty Russell [this message]
2005-12-02  9:01   ` Two module-init- Scott James Remnant
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=1133482376.4094.11.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --cc=greg@kroah.com \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scott@ubuntu.com \
    --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