From: Stephen Rothwell <sfr@canb•auug.org.au>
To: David Miller <davem@davemloft•net>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: sparc tree build warning
Date: Fri, 29 Jan 2010 17:32:20 +1100 [thread overview]
Message-ID: <20100129173220.abdd823d.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100128.201206.257650090.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 772 bytes --]
Hi Dave,
On Thu, 28 Jan 2010 20:12:06 -0800 (PST) David Miller <davem@davemloft•net> wrote:
>
> Simply ignore the warning then, I thought you were reporting
> a build failure.
No worries, I just report warnings in case noone else notices them. And
in case they are important.
> Looking at the specific case of net/core/pktgen.c:867
>
> "len" is variable in the net/core/pktgen.c line that emits the
> warning
>
> Even though it is limited to "sizeof(name) - 1" via strn_len()'s
> third argument, that's a lot to expect the compiler to dig into
> and be able to conclude invariants from.
Yeah, indeed. We need an intuitive compiler :-)
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-01-29 6:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 5:33 linux-next: sparc tree build warning Stephen Rothwell
2009-12-14 7:01 ` David Miller
2009-12-14 8:55 ` Stephen Rothwell
2009-12-14 7:40 ` David Miller
2009-12-14 9:00 ` Stephen Rothwell
2010-01-28 7:44 ` Stephen Rothwell
2010-01-28 13:24 ` David Miller
2010-01-28 23:25 ` Stephen Rothwell
2010-01-29 4:12 ` David Miller
2010-01-29 6:32 ` Stephen Rothwell [this message]
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=20100129173220.abdd823d.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=davem@davemloft$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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