From: Li Zefan <lizf@cn.fujitsu.com>
To: Paul Jackson <pj@sgi.com>
Cc: akpm@linux-foundation.org, menage@google.com,
kamezawa.hiroyu@jp.fujitsu.com, linux-kernel@vger.kernel.org,
containers@lists.linux-foundation.org
Subject: Re: [PATCH 1/7] cgroup: fix and update documentation
Date: Mon, 18 Feb 2008 16:25:14 +0800 [thread overview]
Message-ID: <47B940EA.5000305@cn.fujitsu.com> (raw)
In-Reply-To: <20080218010255.a808714f.pj@sgi.com>
Paul Jackson wrote:
> Li Zefan wrote:
>> *** notify_on_release is disabled in the current patch set. It will be
>> -*** reactivated in a future patch in a less-intrusive manner
>> +*** reactivated in a future patch in a less-intrusive manner.
>
> Someone should verify this, but I'm pretty sure that notify_on_release
> is now working ... no longer disabled. I believe the above line from
> the documentation is out of date.
>
Aha, it does work now. I tried it but it didn't seem to work, maybe I didn't
something wrong. I'll resend a new patch.
next prev parent reply other threads:[~2008-02-18 8:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 5:49 [PATCH 1/7] cgroup: fix and update documentation Li Zefan
2008-02-18 7:02 ` Paul Jackson
[not found] ` <20080218010255.a808714f.pj-sJ/iWh9BUns@public.gmane.org>
2008-02-18 8:25 ` Li Zefan
2008-02-18 8:25 ` Li Zefan [this message]
[not found] ` <47B940EA.5000305-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2008-02-18 8:39 ` Li Zefan
2008-02-18 8:39 ` Li Zefan
[not found] ` <47B94433.4010808-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2008-02-20 3:08 ` Paul Menage
2008-02-20 3:08 ` Paul Menage
[not found] ` <47B91C75.6000907-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2008-02-18 7:02 ` Paul Jackson
-- strict thread matches above, loose matches on Subject: below --
2008-02-18 5:49 Li Zefan
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=47B940EA.5000305@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--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 \
/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.