linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wim Van Sebroeck <wim@iguana.be>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH] watchdogs: fix several MODULE_PARM_DESC strings
Date: Mon, 3 May 2010 10:57:19 +0200	[thread overview]
Message-ID: <20100503085719.GA24325@infomag.iguana.be> (raw)
In-Reply-To: <20100501094615.06fc4972.randy.dunlap@oracle.com>

Hi Randy,

> Fix MODULE_PARM_DESC() strings in several watchdog drivers.
> Some are simple as add a parenthesis.
> Others are problems from __stringify() being used on a
> variable name instead of a macro name, so the variable name
> is produced in the string instead of its build-time value.
> In these cases, create a macro for the value so that the
> module param description string is useful.
> 
> Only pc87413_wdt has been built (due to toolchains).
> 
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> Cc: Wim Van Sebroeck <wim@iguana.be>

Adding this one to the linux-2.6-watchdog-next tree.

> BTW, in ep93xx_wdt.c, I can't find where WATCHDOG_TIMEOUT is
> defined.  Can someone point me to it, please?
> (or does it not even build?)

I don't think it will build: WDT_TIMEOUT is the correct timeout macro.
I'll sent in a fix for this. Thanks!

> --- lnx-2634-rc6.orig/drivers/watchdog/pc87413_wdt.c
> +++ lnx-2634-rc6/drivers/watchdog/pc87413_wdt.c
> @@ -53,7 +53,9 @@
>  #define WDTO                0x11	/* Watchdog timeout register */
>  #define WDCFG               0x12	/* Watchdog config register */
>  
> -static int io = 0x2E;			/* Address used on Portwell Boards */
> +#define IO_DEFAULT	0x2E		/* Address used on Portwell Boards */
> +
> +static int io = IO_DEFAULT;
>  
>  static int timeout = DEFAULT_TIMEOUT;	/* timeout value */
>  static unsigned long timer_enabled;	/* is the timer enabled? */
> @@ -583,12 +585,12 @@ MODULE_LICENSE("GPL");
>  MODULE_ALIAS_MISCDEV(WATCHDOG_MINOR);
>  
>  module_param(io, int, 0);
> -MODULE_PARM_DESC(io, MODNAME " I/O port (default: " __MODULE_STRING(io) ").");
> +MODULE_PARM_DESC(io, MODNAME " I/O port (default: " __MODULE_STRING(IO_DEFAULT) ").");

This one is changed to:
+MODULE_PARM_DESC(io, MODNAME " I/O port (default: "
+                                       __MODULE_STRING(IO_DEFAULT) ").");

Kind regards,
Wim.


      reply	other threads:[~2010-05-03  8:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-01 16:46 [PATCH] watchdogs: fix several MODULE_PARM_DESC strings Randy Dunlap
2010-05-03  8:57 ` Wim Van Sebroeck [this message]

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=20100503085719.GA24325@infomag.iguana.be \
    --to=wim@iguana.be \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    /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;
as well as URLs for NNTP newsgroup(s).