From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: [patch 0/6] s390 patches for 2.6.30-rc3
Date: Thu, 23 Apr 2009 13:46:38 +0200 [thread overview]
Message-ID: <20090423114638.865214111@de.ibm.com> (raw)
Greetings,
another set of patches for s390. Patch #3 is the only one that
is not completely boring, it improves the quality of the idle
cpu accounting field in /proc/stat.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next reply other threads:[~2009-04-23 11:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 11:46 Martin Schwidefsky [this message]
2009-04-23 11:46 ` [patch 1/6] ipl: fix compile breakage Martin Schwidefsky
2009-04-23 11:46 ` [patch 2/6] appldata: avoid deadlock with appldata_mem Martin Schwidefsky
2009-04-23 11:46 ` [patch 3/6] /proc/stat idle field for idle cpus Martin Schwidefsky
2009-04-23 11:46 ` [patch 4/6] Use tape_generic_offline directly Martin Schwidefsky
2009-04-23 11:46 ` [patch 5/6] omit frame pointers on s390 when possible Martin Schwidefsky
2009-04-23 11:46 ` [patch 6/6] update default configuration Martin Schwidefsky
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=20090423114638.865214111@de.ibm.com \
--to=schwidefsky@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
/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