public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: linux-kbuild@vger.kernel.org, zippel@linux-m68k.org,
	lkml <linux-kernel@vger.kernel.org>,
	Nir Tzachar <nir.tzachar@gmail.com>
Subject: Re: [PATCH]scripts/kconfig/nconf.gui.c Fix warning: value computed is not used
Date: Tue, 03 Aug 2010 11:59:39 +0200	[thread overview]
Message-ID: <4C57E88B.8070505@suse.cz> (raw)
In-Reply-To: <1280790966-417-1-git-send-email-justinmattock@gmail.com>

On 3.8.2010 01:16, Justin P. Mattock wrote:
> The below patch fixes some warning messages Im getting when doing
> make nconfig
> 
>  make nconfig
>   HOSTCC  scripts/kconfig/nconf.gui.o
> scripts/kconfig/nconf.gui.c: In function 'print_in_middle':
> scripts/kconfig/nconf.gui.c:170:2: warning: value computed is not used
> scripts/kconfig/nconf.gui.c: In function 'btn_dialog':
> scripts/kconfig/nconf.gui.c:300:2: warning: value computed is not used
> scripts/kconfig/nconf.gui.c:304:2: warning: value computed is not used
> scripts/kconfig/nconf.gui.c: In function 'dialog_inputbox':
> scripts/kconfig/nconf.gui.c:395:2: warning: value computed is not used
> scripts/kconfig/nconf.gui.c:397:2: warning: value computed is not used
> scripts/kconfig/nconf.gui.c:399:2: warning: value computed is not used
> scripts/kconfig/nconf.gui.c:404:2: warning: value computed is not used
> scripts/kconfig/nconf.gui.c: In function 'show_scroll_win':
> scripts/kconfig/nconf.gui.c:534:2: warning: value computed is not used
> scripts/kconfig/nconf.gui.c:549:2: warning: value computed is not used
> scripts/kconfig/nconf.gui.c:551:2: warning: value computed is not used
>   HOSTLD  scripts/kconfig/nconf
> scripts/kconfig/nconf arch/x86/Kconfig
> 
> I looked around for a way to fix these, but am not familiar with ncurses.
> if there's a better way let me know and/or send a seperate fix.
> 
> Signed-off-by: Justin P. Mattock <justinmattock@gmail.com>
> 
> ---
>  scripts/kconfig/nconf.gui.c |   11 -----------
>  1 files changed, 0 insertions(+), 11 deletions(-)
> 
> diff --git a/scripts/kconfig/nconf.gui.c b/scripts/kconfig/nconf.gui.c
> index a9d9344..08a5a04 100644
> --- a/scripts/kconfig/nconf.gui.c
> +++ b/scripts/kconfig/nconf.gui.c
> @@ -167,7 +167,6 @@ void print_in_middle(WINDOW *win,
>  	length = strlen(string);
>  	temp = (width - length) / 2;
>  	x = startx + (int)temp;
> -	wattrset(win, color);

Huh? :) This change makes nconfig look black and white. I'm all for
eliminating warnings, but please do not eliminate features at the same
time (or submit a patch with "Subject: make nconfig black and white" and
do not mask it as warning fixes).

Michal

  reply	other threads:[~2010-08-03 10:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-02 23:16 [PATCH]scripts/kconfig/nconf.gui.c Fix warning: value computed is not used Justin P. Mattock
2010-08-03  9:59 ` Michal Marek [this message]
2010-08-03 13:42   ` Justin P. Mattock
2010-08-03 13:46     ` Nir Tzachar
2010-08-03 14:32       ` Justin P. Mattock
2010-08-03 15:54         ` Nir Tzachar
2010-08-03 16:22           ` Justin P. Mattock

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=4C57E88B.8070505@suse.cz \
    --to=mmarek@suse.cz \
    --cc=justinmattock@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nir.tzachar@gmail.com \
    --cc=zippel@linux-m68k.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