From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
Cc: linux-kernel@vger.kernel.org, akpm <akpm@osdl.org>
Subject: [PATCH] parport_pc: don't mix module parameter styles
Date: Sat, 25 Dec 2004 21:12:23 -0800 [thread overview]
Message-ID: <41CE4837.5080701@osdl.org> (raw)
In-Reply-To: <cqle2s$hrm$1@sea.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
Alexander E. Patrakov wrote:
>
> Here it boots and works, but I can't say that I have done any serious
> testing. The following message appears in the kernel log:
>
> Dec 25 11:38:09 lfs parport_pc: Ignoring new-style parameters in presence of
> obsolete ones
> Dec 25 11:38:09 lfs parport_pc: VIA 686A/8231 detected
> Dec 25 11:38:09 lfs parport_pc: probing current configuration
> Dec 25 11:38:09 lfs parport_pc: Current parallel port base: 0x378
> Dec 25 11:38:09 lfs parport0: PC-style at 0x378 (0x778), irq 7, using FIFO
> [PCSPP,TRISTATE,COMPAT,ECP]
> Dec 25 11:38:09 lfs parport_pc: VIA parallel port: io=0x378, irq=7
>
> I don't understand the first line, and it wasn't there in 2.6.9. Could you
> please explain what it means? I don't pass any parameters to the module. I
> use module-init-tools version 3.0 although I know it is not the latest.
Somehow parport_pc.c ended up with mixed old-style and
new-style module parameters, but mixing them is not
allowed.
Use module_param() instead of MODULE_PARM() -- cannot be mixed.
Signed-off-by: Randy Dunlap <rddunlap@osdl.org>
diffstat:=
drivers/parport/parport_pc.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
[-- Attachment #2: parport_modprm.patch --]
[-- Type: text/x-patch, Size: 1137 bytes --]
Use module_param() instead of MODULE_PARM() -- cannot be mixed.
Signed-off-by: Randy Dunlap <rddunlap@osdl.org>
diffstat:=
drivers/parport/parport_pc.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff -Naurp ./drivers/parport/parport_pc.c~parport_modprm ./drivers/parport/parport_pc.c
--- ./drivers/parport/parport_pc.c~parport_modprm 2004-12-24 13:35:39.000000000 -0800
+++ ./drivers/parport/parport_pc.c 2004-12-25 21:03:35.123264504 -0800
@@ -3176,7 +3176,6 @@ static int __init parport_init_mode_setu
#ifdef MODULE
static const char *irq[PARPORT_PC_MAX_PORTS];
static const char *dma[PARPORT_PC_MAX_PORTS];
-static char *init_mode;
MODULE_PARM_DESC(io, "Base I/O address (SPP regs)");
module_param_array(io, int, NULL, 0);
@@ -3192,8 +3191,9 @@ MODULE_PARM_DESC(verbose_probing, "Log c
module_param(verbose_probing, int, 0644);
#endif
#ifdef CONFIG_PCI
+static char *init_mode;
MODULE_PARM_DESC(init_mode, "Initialise mode for VIA VT8231 port (spp, ps2, epp, ecp or ecpepp)");
-MODULE_PARM(init_mode, "s");
+module_param(init_mode, charp, 0);
#endif
static int __init parse_parport_params(void)
next prev parent reply other threads:[~2004-12-26 5:18 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-24 22:39 Ho ho ho - Linux v2.6.10 Linus Torvalds
2004-12-25 11:11 ` Andrew Walrond
2004-12-25 12:19 ` Alan Cox
2004-12-26 11:30 ` Wichert Akkerman
2004-12-26 13:45 ` R. J. Wysocki
2004-12-26 19:37 ` Pavel Machek
2004-12-26 19:39 ` Pavel Machek
2004-12-26 20:27 ` R. J. Wysocki
2004-12-26 22:10 ` Pavel Machek
2005-01-13 18:09 ` 2.6.10-mm3: swsusp: out of memory on resume (was: Re: Ho ho ho - Linux v2.6.10) Rafael J. Wysocki
2005-01-13 19:59 ` Pavel Machek
2005-01-13 21:22 ` Rafael J. Wysocki
2005-01-14 14:34 ` hugang
2005-01-14 17:25 ` Rafael J. Wysocki
2005-01-15 21:43 ` Rafael J. Wysocki
2005-01-16 21:51 ` Pavel Machek
2005-01-17 14:53 ` Rafael J. Wysocki
2005-01-17 15:22 ` Pavel Machek
2005-01-18 1:44 ` hugang
[not found] ` <200501150042.35377.rjw@sisk.pl>
2005-01-15 1:21 ` hugang
2005-01-15 1:21 ` [Qemu-devel] " hugang
2005-01-15 11:48 ` [Qemu-devel] Re: 2.6.10-mm3: swsusp: out of memory on resume Fabrice Bellard
2005-01-15 16:40 ` hugang
2005-01-16 4:38 ` hugang
2005-01-15 18:02 ` [Qemu-devel] W2K SP0 Status (was: Re: 2.6.10-mm3: swsusp: out of memory on resume) Tim
2005-01-17 18:02 ` [Qemu-devel] Re: Re: 2.6.10-mm3: swsusp: out of memory on resume Ronald
2005-01-17 21:54 ` Fabrice Bellard
2005-01-22 4:17 ` [Qemu-devel] " Anand Kumria
2005-01-22 12:42 ` Johannes Schindelin
[not found] ` <200501151147.32919.rjw@sisk.pl>
[not found] ` <200501152220.42129.rjw@sisk.pl>
2005-01-16 5:54 ` 2.6.10-mm3: swsusp: out of memory on resume (was: Re: Ho ho ho - Linux v2.6.10) hugang
2005-01-16 5:54 ` [Qemu-devel] " hugang
2005-01-16 10:07 ` Rafael J. Wysocki
2005-01-16 10:07 ` [Qemu-devel] " Rafael J. Wysocki
2005-01-16 14:46 ` hugang
2005-01-17 15:48 ` Rafael J. Wysocki
2005-01-17 16:49 ` Rafael J. Wysocki
2004-12-30 9:58 ` Ho ho ho - Linux v2.6.10 Rafael J. Wysocki
2004-12-26 15:45 ` Alan Cox
2004-12-29 12:44 ` Paolo Ciarrocchi
2004-12-26 2:55 ` Bill Davidsen
2004-12-26 3:36 ` Linus Torvalds
[not found] ` <1104171962.18174.28.camel@d845pe>
2004-12-28 16:38 ` Ho ho ho - Linux v2.6.10 (irq18) Bill Davidsen
2004-12-26 4:19 ` Ho ho ho - Linux v2.6.10 Alexander E. Patrakov
2004-12-26 5:12 ` Randy.Dunlap [this message]
2004-12-26 20:35 ` Greg Norris
2004-12-27 1:31 ` Dmitry Torokhov
2004-12-28 2:36 ` Greg Norris
2004-12-27 16:10 ` Ho ho ho - Linux v2.6.10 (compile stats) John Cherry
2004-12-28 1:04 ` Ho ho ho - Linux v2.6.10 Håkan Lindqvist
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=41CE4837.5080701@osdl.org \
--to=rddunlap@osdl.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrakov@ums.usu.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.