public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Foley <pefoley2@verizon.net>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: Peter Foley <pefoley2@verizon.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Kbuild Mailing List <linux-kbuild@vger.kernel.org>,
	mmarek@suse.cz
Subject: Re: [PATCH] kbuild: fix set but not used warnings
Date: Sat, 22 Oct 2011 15:40:09 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LNX.2.00.1110221538570.59156@linux> (raw)
In-Reply-To: <CACqU3MXS6-uE01EVAW1KdCViKioSz_F79YqzYwdTLrmc8hoMAw@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 830 bytes --]

On Sat, 22 Oct 2011, Arnaud Lacombe wrote:

> Hi,
> 
> On Sat, Oct 22, 2011 at 2:01 PM, Peter Foley <pefoley2@verizon.net> wrote:
> > Remove set but not used variables to fix warnings.
> >
> >  HOSTCC  scripts/kconfig/gconf.o
> > /usr/src/lto/scripts/kconfig/gconf.c: In function 'change_sym_value':
> > /usr/src/lto/scripts/kconfig/gconf.c:833:11: warning: variable 'oldval' set but not used [-Wunused-but-set-variable]
> > /usr/src/lto/scripts/kconfig/gconf.c: In function 'update_tree':
> > /usr/src/lto/scripts/kconfig/gconf.c:1281:19: warning: variable 'prop' set but not used [-Wunused-but-set-variable]
> >
> > Signed-off-by: Peter Foley <pefoley2@verizon.net>
> >
> s/kbuild/kconfig/ in the subject, that help to know changes is only
> limited to scripts/kconfig/
> 
>  - Arnaud

Noted. Should I resend this patch? 

Peter

  reply	other threads:[~2011-10-22 20:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-22 18:01 [PATCH] kbuild: fix set but not used warnings Peter Foley
2011-10-22 19:30 ` Arnaud Lacombe
2011-10-22 19:40   ` Peter Foley [this message]
2011-12-11 20:30 ` Michal Marek

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=alpine.LNX.2.00.1110221538570.59156@linux \
    --to=pefoley2@verizon.net \
    --cc=lacombar@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /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