From: Rusty Russell <rusty@rustcorp.com.au>
To: alan@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] 2.2 Trivial patches
Date: Mon, 18 Feb 2002 15:17:31 +1100 [thread overview]
Message-ID: <E16cfF5-0001rX-00@wagner.rustcorp.com.au> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1531 bytes --]
Hi Alan,
Just one trivial patch this week for 2.2.
Cheers!
Rusty.
Trivial patch update against 2.2.21-pre2:
René Scharfe <l.s.r@web.de>: [PATCH] compiler warnings in scripts_tkgen.c:
this patch fixes two compiler warnings during make xconfig which
turn up if one uses -Wshadow
diff -urN -I \$.*\$ --exclude TAGS -X /home/rusty/devel/kernel/kernel-patches/current-dontdiff --minimal /home/rusty/devel/kernel/linux-2.2.21-pre2/scripts/tkgen.c /home/rusty/devel/kernel/trivial-2.2.21-pre2/scripts/tkgen.c
--- /home/rusty/devel/kernel/linux-2.2.21-pre2/scripts/tkgen.c Mon May 28 13:57:45 2001
+++ /home/rusty/devel/kernel/trivial-2.2.21-pre2/scripts/tkgen.c Mon Feb 18 15:15:43 2002
@@ -587,11 +587,11 @@
case token_int:
if ( cfg->value && *cfg->value == '$' )
{
- int index = get_varnum( cfg->value+1 );
+ int i = get_varnum( cfg->value+1 );
printf( "\n" );
- if ( ! vartable[index].global_written )
+ if ( ! vartable[i].global_written )
{
- global( vartable[index].name );
+ global( vartable[i].name );
}
printf( "\t" );
}
@@ -956,7 +956,6 @@
static void end_proc( struct kconfig * scfg, int menu_num )
{
struct kconfig * cfg;
- int i;
printf( "\n\n\n" );
printf( "\tfocus $w\n" );
@@ -1051,6 +1050,7 @@
{
if ( cfg->token == token_tristate )
{
+ int i;
if ( ! vartable[cfg->nameindex].global_written )
{
vartable[cfg->nameindex].global_written = 1;
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
reply other threads:[~2002-02-18 4:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E16cfF5-0001rX-00@wagner.rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=alan@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
all inboxes | Powered by JetHome®