All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: menage@google.com
Cc: akpm@linux-foundation.org, balbir@in.ibm.com, pj@sgi.com,
	Pavel Emelianov <xemul@openvz.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
	linux-kernel@vger.kernel.org,
	containers@lists.linux-foundation.org
Subject: Re: [PATCH 00/10] CGroup API files: Various cleanup to CGroup control files
Date: Tue, 26 Feb 2008 11:23:25 +0800	[thread overview]
Message-ID: <47C3862D.8080603@cn.fujitsu.com> (raw)
In-Reply-To: <20080223224725.115590000@menage.corp.google.com>

menage@google.com wrote:
> This patchset is a roll-up of the non-contraversial items of the
> various patches that I've sent out recently, fixed according to the
> feedback received.
> 
> In summary they are:
> 
> - general rename of read_uint/write_uint to read_u64/write_u64
> 
> - use these methods for cpusets and memory controller files
> 
> - add a read_map cgroup file method, and use it in the memory
>   controller
> 
> - move the "releasable" control file to the debug subsystem
> 
> - make the debug subsystem config option default to "n"
> 
> The only user-visible changes are the movement of the "releasable"
> file and the fact that some write_u64()-based control files are now
> more forgiving of additional whitespace at the end of their input.
> 
> Signed-off-by: Paul Menage <menage@google.com>
> 
> --
> --

Should those pathces be rebased againt 2.6.25-rc3 ?

  parent reply	other threads:[~2008-02-26  3:25 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-23 22:47 [PATCH 00/10] CGroup API files: Various cleanup to CGroup control files menage
2008-02-23 22:47 ` [PATCH 01/10] CGroup API files: Rename read/write_uint methods to read_write_u64 menage-hpIqsD4AKlfQT0dZR+AlfA
2008-02-23 22:47   ` menage
2008-02-23 22:47 ` [PATCH 02/10] CGroup API files: Add res_counter_read_u64() menage-hpIqsD4AKlfQT0dZR+AlfA
2008-02-23 22:47 ` menage
2008-02-23 22:47 ` [PATCH 03/10] CGroup API files: Use read_u64 in memory controller menage-hpIqsD4AKlfQT0dZR+AlfA
2008-02-23 22:47   ` menage
2008-02-23 22:47 ` [PATCH 04/10] CGroup API files: Strip all trailing whitespace in cgroup_write_u64 menage-hpIqsD4AKlfQT0dZR+AlfA
2008-02-23 22:47 ` menage
2008-02-23 22:47 ` [PATCH 05/10] CGroup API files: Update cpusets to use cgroup structured file API menage-hpIqsD4AKlfQT0dZR+AlfA
2008-02-23 22:47 ` menage
     [not found]   ` <20080223232617.958345000-B63HFAS8fGlSzHKm+aFRNNkmqwFzkYv6@public.gmane.org>
2008-02-27  0:54     ` Li Zefan
2008-02-27  0:54   ` Li Zefan
2008-02-27  1:09     ` Paul Menage
     [not found]     ` <47C4B4B0.4010700-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2008-02-27  1:09       ` Paul Menage
2008-02-23 22:47 ` [PATCH 06/10] CGroup API files: Add cgroup map data type menage-hpIqsD4AKlfQT0dZR+AlfA
2008-02-23 22:47 ` menage
2008-02-23 22:47 ` [PATCH 07/10] CGroup API files: Use cgroup map for memcontrol stats file menage
2008-02-23 22:47 ` menage-hpIqsD4AKlfQT0dZR+AlfA
2008-02-23 22:47 ` [PATCH 08/10] CGroup API files: Drop mem_cgroup_force_empty() menage-hpIqsD4AKlfQT0dZR+AlfA
2008-02-23 22:47 ` menage
2008-02-23 22:47 ` [PATCH 09/10] CGroup API files: Move "releasable" to cgroup_debug subsystem menage-hpIqsD4AKlfQT0dZR+AlfA
2008-02-23 22:47 ` menage
2008-02-23 22:47 ` [PATCH 10/10] CGroup API files: Make CGROUP_DEBUG default to off menage-hpIqsD4AKlfQT0dZR+AlfA
2008-02-23 22:47   ` menage
     [not found] ` <20080223224725.115590000-B63HFAS8fGlSzHKm+aFRNNkmqwFzkYv6@public.gmane.org>
2008-02-26  3:23   ` [PATCH 00/10] CGroup API files: Various cleanup to CGroup control files Li Zefan
2008-02-26  3:23 ` Li Zefan [this message]
     [not found]   ` <47C3862D.8080603-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2008-02-26  6:19     ` Paul Menage
2008-02-26  6:19   ` Paul Menage
     [not found]     ` <6599ad830802252219p77f41917u7c6c137c8e5448e0-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-02-26  7:48       ` Li Zefan
2008-02-26  7:48     ` Li Zefan
2008-02-27  1:09       ` Paul Menage
     [not found]       ` <47C3C462.4000706-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2008-02-27  1:09         ` Paul Menage
  -- strict thread matches above, loose matches on Subject: below --
2008-02-23 22:47 menage-hpIqsD4AKlfQT0dZR+AlfA

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=47C3862D.8080603@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@in.ibm.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menage@google.com \
    --cc=pj@sgi.com \
    --cc=xemul@openvz.org \
    --cc=yamamoto@valinux.co.jp \
    /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.