From: Rusty Russell <rusty@rustcorp.com.au>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-input@atrey.karlin.mff.cuni.cz,
Scott James Remnant <scott@ubuntu.com>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>,
vojtech@suse.cz
Subject: Re: Two module-init-
Date: Sun, 04 Dec 2005 21:24:25 +1100 [thread overview]
Message-ID: <1133691865.30188.24.camel@localhost.localdomain> (raw)
In-Reply-To: <200512022328.29182.dtor_core@ameritech.net>
On Fri, 2005-12-02 at 23:28 -0500, Dmitry Torokhov wrote:
> On Friday 02 December 2005 23:19, Dmitry Torokhov wrote:
> > On Thursday 01 December 2005 19:12, Rusty Russell wrote:
> > > Meanwhile, as noone seems to use swbit in struct input_device_id,
> > > perhaps we can remove it for 2.6.15?
> > >
> >
> > Please take a look at drivers/input/keyboard/corgikbd.c
> >
>
> What I meant we do use EV_SW in the drivers and so it sould be part
> of input_device_id. Nobody uses ffbit or sndbit either and still
> they are present...
Sure. BUT it will break current users. I'm suggesting we jerk that
field out for 2.6.15, and reintroduce it for >= 2.6.16, when we can (1)
ensure everyone has a fixed module-init tools, or (2) make sure everyone
is using the module alias stuff, or both.
It seems the simplest solution, surely?
Rusty.
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
next prev parent reply other threads:[~2005-12-04 10:24 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
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 [this message]
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=1133691865.30188.24.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=dtor_core@ameritech.net \
--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