On Tue, 11 Sep 2007 15:41:02 -0400 (EDT) Robert P. J. Day wrote:
>
> in drivers/net/wan/dscc4.c, you have the snippet:
>
> =====
> #ifndef MODULE
> static int __init dscc4_setup(char *str)
> {
> int *args[] = { &debug, &quartz, NULL }, **p = args;
>
> while (*p && (get_option(&str, *p) == 2))
> p++;
> return 1;
> }
>
> __setup("dscc4.setup=", dscc4_setup);
> #endif
> =====
>
> but is that call to __setup() correct? i thought you would just use
>
> __setup("setup=", dscc4_setup);
>
> but you * would* specify "dscc4.setup=" on the boot line and that
> would properly be associated with that setup routine if that code were
> compiled into the kernel.
>
> or am i totally misreading how this mechanism works?
You are correct AFAIK. Please check with the driver maintainer:
DSCC4 DRIVER
P: Francois Romieu
M: romieu@xxxxxxxxxxxxx
L: netdev@xxxxxxxxxxxxxxx
S: Maintained
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
