public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* 10 New compile/sparse warnings (overnight build)
@ 2004-09-09 14:57 John Cherry
  2004-09-09 16:39 ` John Cherry
  0 siblings, 1 reply; 4+ messages in thread
From: John Cherry @ 2004-09-09 14:57 UTC (permalink / raw)
  To: linux-kernel@vger.kernel.org


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>




^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: 10 New compile/sparse warnings (overnight build)
  2004-09-09 14:57 10 New compile/sparse warnings (overnight build) John Cherry
@ 2004-09-09 16:39 ` John Cherry
  2004-09-09 17:29   ` Dave Jones
  0 siblings, 1 reply; 4+ messages in thread
From: John Cherry @ 2004-09-09 16:39 UTC (permalink / raw)
  To: linux-kernel@vger.kernel.org

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/


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: 10 New compile/sparse warnings (overnight build)
  2004-09-09 16:39 ` John Cherry
@ 2004-09-09 17:29   ` Dave Jones
  2004-09-09 18:22     ` John Cherry
  0 siblings, 1 reply; 4+ messages in thread
From: Dave Jones @ 2004-09-09 17:29 UTC (permalink / raw)
  To: John Cherry; +Cc: linux-kernel@vger.kernel.org

On Thu, Sep 09, 2004 at 09:39:27AM -0700, John Cherry wrote:
 > Sorry about the duplicate entries.  I'll fix the tool.  There are really
 > just 7 new sparse warnings.

Out of curiosity, how often is the sparse binary being updated
in this automated check ?

		Dave


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: 10 New compile/sparse warnings (overnight build)
  2004-09-09 17:29   ` Dave Jones
@ 2004-09-09 18:22     ` John Cherry
  0 siblings, 0 replies; 4+ messages in thread
From: John Cherry @ 2004-09-09 18:22 UTC (permalink / raw)
  To: Dave Jones; +Cc: linux-kernel@vger.kernel.org

The sparse binary is being updated every two weeks.  I am trying to
avoid mining reasonable data with a changing kernel AND a changing
sparse tool.

John

On Thu, 2004-09-09 at 10:29, Dave Jones wrote:
> On Thu, Sep 09, 2004 at 09:39:27AM -0700, John Cherry wrote:
>  > Sorry about the duplicate entries.  I'll fix the tool.  There are really
>  > just 7 new sparse warnings.
> 
> Out of curiosity, how often is the sparse binary being updated
> in this automated check ?
> 
> 		Dave


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2004-09-09 18:29 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-09-09 14:57 10 New compile/sparse warnings (overnight build) John Cherry
2004-09-09 16:39 ` John Cherry
2004-09-09 17:29   ` Dave Jones
2004-09-09 18:22     ` John Cherry

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox