From: Chuck Short <zulcss@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: [KJ] [PATCH] net/ipv4/route warnings
Date: Mon, 30 May 2005 02:09:23 +0000 [thread overview]
Message-ID: <429A75D3.3030808@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 100 bytes --]
This patch fixes gcc4 warnings in net/ipv4/route.c
Signed-off by: Chuck Short <zulcss@gmail.com>
[-- Attachment #2: ipv4-route_gcc4_warning --]
[-- Type: text/plain, Size: 1171 bytes --]
diff -Naur linux-source-2.6.12-2.6.11.93.orig/net/ipv4/route.c linux-source-2.6.12-2.6.11.93/net/ipv4/route.c
--- linux-source-2.6.12-2.6.11.93.orig/net/ipv4/route.c 2005-05-08 02:11:18.000000000 -0400
+++ linux-source-2.6.12-2.6.11.93/net/ipv4/route.c 2005-05-29 14:32:35.464664496 -0400
@@ -1767,7 +1767,7 @@
struct in_device *in_dev,
u32 daddr, u32 saddr, u32 tos)
{
- struct rtable* rth;
+ struct rtable* rth = NULL;
int err;
unsigned hash;
@@ -1794,7 +1794,7 @@
u32 daddr, u32 saddr, u32 tos)
{
#ifdef CONFIG_IP_ROUTE_MULTIPATH_CACHED
- struct rtable* rth;
+ struct rtable* rth = NULL;
unsigned char hop, hopcount, lasthop;
int err = -EINVAL;
unsigned int hash;
@@ -2239,7 +2239,7 @@
struct net_device *dev_out,
unsigned flags)
{
- struct rtable *rth;
+ struct rtable *rth = NULL;
int err = __mkroute_output(&rth, res, fl, oldflp, dev_out, flags);
unsigned hash;
if (err == 0) {
@@ -2267,7 +2267,7 @@
unsigned char hop;
unsigned hash;
int err = -EINVAL;
- struct rtable *rth;
+ struct rtable *rth = NULL;
if (res->fi && res->fi->fib_nhs > 1) {
unsigned char hopcount = res->fi->fib_nhs;
[-- Attachment #3: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
reply other threads:[~2005-05-30 2:09 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=429A75D3.3030808@gmail.com \
--to=zulcss@gmail.com \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.