From: Lightweight patch manager <patch@luckynet.dynu.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Kernel Build -- Daniel Phillips <phillips@bonn-fries.net>,
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
Keith Owens <kaos@ocs.com.au>,
Linus Torvalds <torvalds@transmeta.com>
Subject: [PATCH] kbuild-2.5: get rid of warnings in split-include and mkdep
Date: Sun, 2 Jun 2002 13:47:25 -0600 (MDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0206021300590.14017-100000@hawkeye.luckynet.adm> (raw)
kbuild-2.5: this patch gets rid of compiletime warnings for mkdep.c and
split-include.c
It is also available at
<URL:ftp://luckynet.dynu.com/pub/linux/kbuild-2.5/kbuild-2.5-noscriptwarnings.patch>
diff -Nur kbuild-2.5/scripts/mkdep.c kbuild-2.5/scripts/mkdep.c
--- kbuild-2.5/scripts/mkdep.c Sat Jun 1 16:19:33 2002
+++ kbuild-2.5/scripts/mkdep.c Sat Jun 1 16:19:33 2002 +0000 thunder (thunder-2.5/scripts/mkdep.c 1.1 0644)
@@ -268,7 +268,7 @@
for (i = 0; i < len; i++) {
char c = name[i];
- if (isupper(c)) c = tolower(c);
+ if (isupper((int)c)) c = tolower((int)c);
if (c == '_') c = '/';
pc[i] = c;
}
@@ -496,7 +496,7 @@
/* \<CONFIG_(\w*) */
cee:
- if (next >= map+2 && (isalnum(next[-2]) || next[-2] == '_'))
+ if (next >= map+2 && (isalnum((int)next[-2]) || next[-2] == '_'))
goto start;
GETNEXT NOTCASE('O', __start);
GETNEXT NOTCASE('N', __start);
diff -Nur kbuild-2.5/scripts/split-include.c kbuild-2.5/scripts/split-include.c
--- kbuild-2.5/scripts/split-include.c Sat Jun 1 16:19:32 2002
+++ kbuild-2.5/scripts/split-include.c Sat Jun 1 16:19:32 2002 +0000 thunder (thunder-2.5/scripts/split-include.c 1.1 0644)
@@ -115,10 +115,10 @@
/* Make the output file name. */
str_config += sizeof("CONFIG_") - 1;
- for (itarget = 0; !isspace(str_config[itarget]); itarget++)
+ for (itarget = 0; !isspace((int)str_config[itarget]); itarget++)
{
char c = str_config[itarget];
- if (isupper(c)) c = tolower(c);
+ if (isupper((int)c)) c = tolower((int)c);
if (c == '_') c = '/';
ptarget[itarget] = c;
}
--
Lightweight patch manager using pine. If you have any objections, tell me.
reply other threads:[~2002-06-02 19:47 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=Pine.LNX.4.44.0206021300590.14017-100000@hawkeye.luckynet.adm \
--to=patch@luckynet.dynu.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
--cc=torvalds@transmeta.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).