From: Martin Schwidefsky <schwidefsky@de•ibm.com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org
Subject: git tree with cputime changes
Date: Mon, 03 Nov 2008 16:10:54 +0100 [thread overview]
Message-ID: <1225725054.24817.15.camel@localhost> (raw)
Hi Stephen,
I've created the cputime git branch on git390.osdl.marist.edu with the
improvements for the idle time accounting. I've got feedback from the
ia64 and powerpc maintainers but nothing really conclusive yet. To find
potential problems it would be nice if you could add
git://git390.osdl.marist.edu/pub/scm/linux-2.6.git cputime
to linux-next. The branch has four patches:
Martin Schwidefsky (4):
[S390] fix scaled & unscaled cputime accounting
[S390] idle cputime accounting
[S390] improve precision of idle accounting.
[S390] improve idle cputime accounting
Thanks in advance..
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next reply other threads:[~2008-11-03 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 15:10 Martin Schwidefsky [this message]
2008-11-04 15:01 ` git tree with cputime changes Stephen Rothwell
2008-11-04 15:32 ` Martin Schwidefsky
2008-11-04 21:48 ` Stephen Rothwell
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=1225725054.24817.15.camel@localhost \
--to=schwidefsky@de$(echo .)ibm.com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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