From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Tejun Heo <tj@kernel.org>, Li Zefan <lizefan@huawei.com>,
LKML <linux-kernel@vger.kernel.org>,
Glauber Costa <glommer@parallels.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>
Subject: Re: [PATCH 1/2] res_counter: Merge res_counter_charge and res_counter_charge_nofail
Date: Wed, 25 Apr 2012 09:28:53 +0900 [thread overview]
Message-ID: <4F974545.1060107@jp.fujitsu.com> (raw)
In-Reply-To: <1335309096-12886-2-git-send-email-fweisbec@gmail.com>
(2012/04/25 8:11), Frederic Weisbecker wrote:
> These two functions do almost the same thing and duplicate some code.
> Merge their implementation into a single common function.
> res_counter_charge_locked() takes one more parameter but it doesn't seem
> to be used outside res_counter.c yet anyway.
>
> There is no (intended) change in the behaviour.
>
> Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
> Cc: Tejun Heo <tj@kernel.org>
> Cc: Li Zefan <lizefan@huawei.com>
> Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> Cc: Glauber Costa <glommer@parallels.com>
> Cc: Kirill A. Shutemov <kirill@shutemov.name>
Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
next prev parent reply other threads:[~2012-04-25 0:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 23:11 [PATCH 0/2] res_counter: Merge some common code Frederic Weisbecker
2012-04-24 23:11 ` [PATCH 1/2] res_counter: Merge res_counter_charge and res_counter_charge_nofail Frederic Weisbecker
2012-04-25 0:28 ` KAMEZAWA Hiroyuki [this message]
2012-04-25 14:40 ` Glauber Costa
2012-04-27 21:37 ` Tejun Heo
2012-04-24 23:11 ` [PATCH 2/2] res_counter: Account max_usage when calling res_counter_charge_nofail() Frederic Weisbecker
2012-04-25 0:29 ` KAMEZAWA Hiroyuki
2012-04-25 14:40 ` Glauber Costa
2012-04-27 21:38 ` Tejun Heo
2012-04-25 2:22 ` [PATCH 0/2] res_counter: Merge some common code Kirill A. Shutemov
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=4F974545.1060107@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=fweisbec@gmail.com \
--cc=glommer@parallels.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=tj@kernel.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.