public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: jbaron@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel/module: fix warning when !CONFIG_DYNAMIC_PRINTK_DEBUG
Date: Wed, 20 Aug 2008 07:24:53 -0700	[thread overview]
Message-ID: <20080820142453.GA31886@suse.de> (raw)
In-Reply-To: <20080820141329.GB7622@orion>

On Wed, Aug 20, 2008 at 06:13:29PM +0400, Alexander Beregalov wrote:
> From: Alexander Beregalov <a.beregalov@gmail.com>
> 
> kernel/module.c: In function 'load_module':
> kernel/module.c:1839: warning: unused variable 'value'
> kernel/module.c:1838: warning: unused variable 'iter'
> 
> 
> Signed-off-by: Alexander Beregalov <a.beregalov@gmail.com>
> ---
> 
>  kernel/module.c |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/kernel/module.c b/kernel/module.c
> index 1721320..5a1258e 100644
> --- a/kernel/module.c
> +++ b/kernel/module.c
> @@ -1835,8 +1835,10 @@ static struct module *load_module(void __user *umod,
>  	unsigned int markersindex;
>  	unsigned int markersstringsindex;
>  	unsigned int verboseindex;
> +#ifdef CONFIG_DYNAMIC_PRINTK_DEBUG
>  	struct mod_debug *iter;
>  	unsigned long value;
> +#endif

Hm, that's not very nice, we try to keep #ifdefs out of the .c file
where ever possible, especially within a single function.  I'll split
the section out of this function that has the #ifdef which should fix
this problem.

thanks,

greg k-h

  reply	other threads:[~2008-08-20 14:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20 14:13 [PATCH] kernel/module: fix warning when !CONFIG_DYNAMIC_PRINTK_DEBUG Alexander Beregalov
2008-08-20 14:24 ` Greg KH [this message]
2008-08-20 15:13   ` Greg KH
2008-08-21 20:35     ` Jason Baron
2008-08-21 20:45       ` Jason Baron
2008-09-11  9:31         ` Greg KH

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=20080820142453.GA31886@suse.de \
    --to=gregkh@suse.de \
    --cc=a.beregalov@gmail.com \
    --cc=jbaron@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /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