From: Andrew Morton <akpm@linux-foundation.org>
To: Michael Holzheu <holzheu@linux.vnet.ibm.com>
Cc: Balbir Singh <balbir@linux.vnet.ibm.com>,
Oleg Nesterov <oleg@redhat.com>,
Shailabh Nagar <nagar1234@in.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-kernel@vger.kernel.org, Jeff Mahoney <jeffm@suse.com>,
Mel Gorman <mel@csn.ul.ie>
Subject: Re: [PATCH 0/2] taskstats: Cleanup patches
Date: Tue, 28 Sep 2010 13:51:17 -0700 [thread overview]
Message-ID: <20100928135117.4fdd5799.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100928142058.796669370@linux.vnet.ibm.com>
On Tue, 28 Sep 2010 16:20:58 +0200
Michael Holzheu <holzheu@linux.vnet.ibm.com> wrote:
> Hello Andrew,
>
> It would be great, if you could accept the taskstats cleanup patches that
> are the prerequisite for the taskstats precise accounting patches. The
> patches do not add any new functionality. I think they make the code better
> readable and extensible:
> * 01/02: taskstats: Separate taskstats commands
> * 02/02: taskstats: Split fill_pid function
>
Sure.
I've been sitting on a couple of taskstats patches for ages. Mel's
delay-accounting-re-implement-c-for-getdelaysc-to-report-information-on-a-target-command.patch
and Jeff's delayacct-align-to-8-byte-boundary-on-64-bit-systems.patch.
I have notes against both of these indicating that Balbir had concerns
and as far as I know those concerns remain unresolved. So I'll drop
those patches now - can you guys please reactivate them if you still
think we should be making these changes?
next prev parent reply other threads:[~2010-09-28 20:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 14:20 [PATCH 0/2] taskstats: Cleanup patches Michael Holzheu
2010-09-28 14:20 ` [PATCH 1/2] taskstats: Separate taskstats commands Michael Holzheu
2010-09-28 14:21 ` [PATCH 2/2] taskstats: Split fill_pid function Michael Holzheu
2010-09-28 20:51 ` Andrew Morton [this message]
2010-09-29 7:50 ` [PATCH 0/2] taskstats: Cleanup patches Balbir Singh
2010-09-29 18:01 ` Andrew Morton
2010-10-02 16:41 ` Balbir Singh
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=20100928135117.4fdd5799.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=holzheu@linux.vnet.ibm.com \
--cc=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=nagar1234@in.ibm.com \
--cc=oleg@redhat.com \
--cc=schwidefsky@de.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.