linux-kernel - Re: linux-next: cputime tree build warning

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 19 May 2009 10:47:00 +0200
From:	Martin Schwidefsky <schwidefsky@...ibm.com>
To:	"Abbott, MG (Michael)" <michael.abbott@...mond.ac.uk>
Cc:	"Stephen Rothwell" <sfr@...b.auug.org.au>,
	<linux-next@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: cputime tree build warning

On Tue, 19 May 2009 08:39:32 +0100
"Abbott, MG (Michael)" <michael.abbott@...mond.ac.uk> wrote:

> > Today's linux-next build (x86_64 allmodconfig) produced this warning:
> > 
> > fs/proc/uptime.c: In function 'uptime_proc_show':
> > fs/proc/uptime.c:14: warning: unused variable 'len'
> > 
> > Introduced by commit ed7e789abfc433e46524419b7cc51d949552505e 
> > ("[PATCH]
> > Fix idle time field in /proc/uptime") from the cputime tree.
> 
> Ouch.  I do apologise.  The (now) bogus variable len must have been
> preserved when I rebased from 2.6.29.3 to current git, and I guess I
> didn't spot the warning among all the other warnings in the build.
 
I'll fix the two problems with the patch: 1) remove len, 2) use
cputime_zero to initialize idletime and update the cputime branch.

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/