public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Andi Kleen <ak@suse.de>,
	"Marcos D. Marado Torres" <marado@student.dei.uc.pt>
Cc: rusty@rustcorp.com.au, linux-kernel@vger.kernel.org,
	akpm@osdl.org, vojtech@suse.cz
Subject: Re: mouse configuration in 2.6.1
Date: Wed, 21 Jan 2004 08:09:25 -0500	[thread overview]
Message-ID: <200401210809.25187.dtor_core@ameritech.net> (raw)
In-Reply-To: <20040121134204.73e6450f.ak@suse.de>

On Wednesday 21 January 2004 07:42 am, Andi Kleen wrote:
> On Wed, 21 Jan 2004 12:31:21 +0000 (WET)
>
> "Marcos D. Marado Torres" <marado@student.dei.uc.pt> wrote:
> > apparently:
> > > psmouse_base.psmouse_proto=bare
> >
> > Actually it's psmouse.proto=bare
>
> In 2.6.1 it is definitely psmouse_base.psmouse_proto=bare
>

You really should see psmouse.psmouse_proto=bare in 2.6.1 (and it's
changed to psmouse.proto=bare in 2.6.2-rc1):

make KBUILD_MODULES=1 -f scripts/Makefile.build obj=drivers/input/mouse
  gcc -Wp,-MD,drivers/input/mouse/.psmouse-base.o.d -nostdinc -iwithprefix
  include -D__KERNEL__ -Iinclude  -D__KERNEL__ -Iinclude  
  -Wall -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common
  -pipe -mpreferred-stack-boundary=2 -march=pentium3
  -Iinclude/asm-i386/mach-default -O2
  -DMODULE -DKBUILD_BASENAME=psmouse_base -DKBUILD_MODNAME=psmouse 
  -c -o drivers/input/mouse/.tmp_psmouse-base.o 
  drivers/input/mouse/psmouse-base.c

As you can see KBUILD_MODNAME is just psmouse and module_param() uses it
as a prefix.

-- 
Dmitry

  parent reply	other threads:[~2004-01-21 13:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040115225948.6b994a48.akpm@osdl.org.suse.lists.linux.kernel>
     [not found] ` <20040118001217.GE3125@werewolf.able.es.suse.lists.linux.kernel>
     [not found]   ` <20040117215535.0e4674b8.akpm@osdl.org.suse.lists.linux.kernel>
     [not found]     ` <20040118081128.GA3153@werewolf.able.es.suse.lists.linux.kernel>
     [not found]       ` <20040118001708.09291455.akpm@osdl.org.suse.lists.linux.kernel>
     [not found]         ` <20040119224219.65991501.rusty@rustcorp.com.au.suse.lists.linux.kernel>
2004-01-19 12:40           ` 2.6.1-mm4 Andi Kleen
2004-01-21  4:06             ` 2.6.1-mm4 Rusty Russell
2004-01-21  4:56               ` 2.6.1-mm4 Valdis.Kletnieks
2004-01-21  8:40               ` 2.6.1-mm4 Vojtech Pavlik
2004-01-21 12:27                 ` 2.6.1-mm4 Andi Kleen
2004-01-21 12:34                   ` 2.6.1-mm4 Vojtech Pavlik
2004-01-21 12:46                     ` 2.6.1-mm4 Andi Kleen
2004-01-21 13:13                       ` 2.6.1-mm4 Vojtech Pavlik
2004-01-22  1:31                       ` 2.6.1-mm4 Rusty Russell
2004-01-21 12:53                     ` 2.6.1-mm4 Dmitry Torokhov
2004-01-21 12:23               ` mouse configuration in 2.6.1 Andi Kleen
2004-01-21 12:31                 ` Marcos D. Marado Torres
2004-01-21 12:42                   ` Andi Kleen
2004-01-21 12:53                     ` Marcos D. Marado Torres
2004-01-21 13:02                       ` Andi Kleen
2004-01-21 13:06                         ` Marcos D. Marado Torres
2004-01-21 13:09                     ` Dmitry Torokhov [this message]
2004-01-21 12:32                 ` Vojtech Pavlik
2004-01-22  1:14                 ` 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=200401210809.25187.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marado@student.dei.uc.pt \
    --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