From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: "Abbott, MG (Michael)" <michael.abbott@diamond.ac.uk>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: cputime tree build warning
Date: Tue, 19 May 2009 10:47:00 +0200 [thread overview]
Message-ID: <20090519104700.57770120@skybase> (raw)
In-Reply-To: <4854F2500EA8C4478A508D2D92973E52046B8498@EXCHANGE25.fed.cclrc.ac.uk>
On Tue, 19 May 2009 08:39:32 +0100
"Abbott, MG (Michael)" <michael.abbott@diamond.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.
prev parent reply other threads:[~2009-05-19 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 7:32 linux-next: cputime tree build warning Stephen Rothwell
2009-05-19 7:39 ` Abbott, MG (Michael)
2009-05-19 8:47 ` Martin Schwidefsky [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=20090519104700.57770120@skybase \
--to=schwidefsky@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=michael.abbott@diamond.ac.uk \
--cc=sfr@canb.auug.org.au \
/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