From: John Cherry <cherry@osdl.org>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 10 New compile/sparse warnings (overnight build)
Date: Thu, 09 Sep 2004 09:39:27 -0700 [thread overview]
Message-ID: <1094747967.2468.35.camel@cherrybomb.pdx.osdl.net> (raw)
In-Reply-To: <1094741838.4142.6.camel@cherrybomb.pdx.osdl.net>
Sorry about the duplicate entries. I'll fix the tool. There are really
just 7 new sparse warnings.
John
On Thu, 2004-09-09 at 07:57, John Cherry wrote:
> Summary:
> New warnings = 10
> Fixed warnings = 2
>
> New warnings:
> -------------
> net/ipv4/ipconfig.c:969:10: warning: undefined identifier 'i'
> net/ipv4/ipconfig.c:969:10: warning: generating address of non-lvalue
>
> net/ipv4/ipconfig.c:969:10: warning: undefined identifier 'i'
> net/ipv4/ipconfig.c:969:10: warning: generating address of non-lvalue
>
> net/ipv4/ipconfig.c:969:32: warning: undefined identifier 'i'
>
> net/ipv4/ipconfig.c:969:39: warning: unknown expression (7 46)
>
> net/ipv4/ipconfig.c:970:18: warning: unknown expression (7 46)
>
> net/ipv4/ipconfig.c:970:31: warning: undefined identifier 'i'
> net/ipv4/ipconfig.c:970:31: warning: generating address of non-lvalue
> net/ipv4/ipconfig.c:970:31: warning: loading unknown expression
>
> net/ipv4/ipconfig.c:970:31: warning: undefined identifier 'i'
> net/ipv4/ipconfig.c:970:31: warning: generating address of non-lvalue
> net/ipv4/ipconfig.c:970:31: warning: loading unknown expression
>
> net/ipv4/ipconfig.c:970:31: warning: undefined identifier 'i'
> net/ipv4/ipconfig.c:970:31: warning: generating address of non-lvalue
> net/ipv4/ipconfig.c:970:31: warning: loading unknown expression
>
> net/ipv4/ipconfig.c:971:16: warning: unknown expression (7 46)
>
> net/ipv4/ipconfig.c:971:9: warning: undefined identifier 'i'
>
>
> Fixed warnings:
> ---------------
> fs/coda/file.c:298:14: warning: incorrect type in initializer
> (incompatible argument 5 (different address spaces))
> fs/coda/file.c:298:14: expected int [usertype] ( *sendfile )( ... )
> fs/coda/file.c:298:14: got int [usertype] ( static [addressable]
> [toplevel] *<noident> )( ... )
>
> fs/coda/file.c:61:66: warning: incorrect type in argument 5 (different
> address spaces)
> fs/coda/file.c:61:66: expected void *<noident>
> fs/coda/file.c:61:66: got void [noderef] *target<asn:1>
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2004-09-09 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 14:57 John Cherry
2004-09-09 16:39 ` John Cherry [this message]
2004-09-09 17:29 ` Dave Jones
2004-09-09 18:22 ` John Cherry
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=1094747967.2468.35.camel@cherrybomb.pdx.osdl.net \
--to=cherry@osdl.org \
--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®