From: Paul Menage <menage@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.32 -mm merge plans (cgroups)
Date: Tue, 15 Sep 2009 17:40:15 -0700 [thread overview]
Message-ID: <6599ad830909151740n2affe0daw27618ccae9c737d6@mail.gmail.com> (raw)
On Tue, Sep 15, 2009 at 4:15 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> cgroups-make-unlock-sequence-in-cgroup_get_sb-consistent.patch
> cgroups-support-named-cgroups-hierarchies.patch
> cgroups-move-the-cgroup-debug-subsys-into-cgroupc-to-access-internal-state.patch
> cgroups-add-a-back-pointer-from-struct-cg_cgroup_link-to-struct-cgroup.patch
> cgroups-allow-cgroup-hierarchies-to-be-created-with-no-bound-subsystems.patch
I think these first five should be fine for merge.
> cgroups-revert-cgroups-fix-pid-namespace-bug.patch
> cgroups-add-a-read-only-procs-file-similar-to-tasks-that-shows-only-unique-tgids.patch
> cgroups-ensure-correct-concurrent-opening-reading-of-pidlists-across-pid-namespaces.patch
> cgroups-use-vmalloc-for-large-cgroups-pidlist-allocations.patch
> cgroups-change-css_set-freeing-mechanism-to-be-under-rcu.patch
> cgroups-let-ss-can_attach-and-ss-attach-do-whole-threadgroups-at-a-time.patch
> cgroups-let-ss-can_attach-and-ss-attach-do-whole-threadgroups-at-a-time-fix.patch
> #cgroups-add-functionality-to-read-write-lock-clone_thread-forking-per-threadgroup.patch: Oleg conniptions
> cgroups-add-functionality-to-read-write-lock-clone_thread-forking-per-threadgroup.patch
> cgroups-add-functionality-to-read-write-lock-clone_thread-forking-per-threadgroup-fix.patch
> cgroups-add-ability-to-move-all-threads-in-a-process-to-a-new-cgroup-atomically.patch
How much longer is the merge window open for? It's probably safest to
hold these in -mm for now since we've not resolved the potential races
in the signal handler accesses; I'll try to find some time to work on
them this week or next.
Paul
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2009-09-16 0:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 0:40 Paul Menage [this message]
2009-09-16 1:42 ` 2.6.32 -mm merge plans (cgroups) Andrew Morton
2009-09-17 23:34 ` Paul Menage
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=6599ad830909151740n2affe0daw27618ccae9c737d6@mail.gmail.com \
--to=menage@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).