From: Zefan Li <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2/2 cgroup/for-3.20] cgroup: add dummy css_put() for !CONFIG_CGROUPS
Date: Wed, 7 Jan 2015 11:57:14 +0800 [thread overview]
Message-ID: <54ACAE9A.1000701@huawei.com> (raw)
In-Reply-To: <20150106165815.GJ3077-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
On 2015/1/7 0:58, Tejun Heo wrote:
> This will later be depended upon by the scheduled cgroup writeback
> support.
>
> Signed-off-by: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Acked-by: Zefan Li <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
WARNING: multiple messages have this Message-ID (diff)
From: Zefan Li <lizefan@huawei.com>
To: Tejun Heo <tj@kernel.org>
Cc: <cgroups@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2 cgroup/for-3.20] cgroup: add dummy css_put() for !CONFIG_CGROUPS
Date: Wed, 7 Jan 2015 11:57:14 +0800 [thread overview]
Message-ID: <54ACAE9A.1000701@huawei.com> (raw)
In-Reply-To: <20150106165815.GJ3077@htj.dyndns.org>
On 2015/1/7 0:58, Tejun Heo wrote:
> This will later be depended upon by the scheduled cgroup writeback
> support.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
Acked-by: Zefan Li <lizefan@huawei.com>
next prev parent reply other threads:[~2015-01-07 3:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 16:57 [PATCH 1/2 cgroup/for-3.20] cgroup: reorder SUBSYS(blkio) in cgroup_subsys.h Tejun Heo
2015-01-06 16:57 ` Tejun Heo
2015-01-06 16:58 ` [PATCH 2/2 cgroup/for-3.20] cgroup: add dummy css_put() for !CONFIG_CGROUPS Tejun Heo
[not found] ` <20150106165815.GJ3077-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2015-01-07 3:57 ` Zefan Li [this message]
2015-01-07 3:57 ` Zefan Li
2015-01-07 3:57 ` [PATCH 1/2 cgroup/for-3.20] cgroup: reorder SUBSYS(blkio) in cgroup_subsys.h Zefan Li
2015-01-07 3:57 ` Zefan Li
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=54ACAE9A.1000701@huawei.com \
--to=lizefan-hv44wf8li93qt0dzr+alfa@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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 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.