From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Seth Jennings <sjenning@linux.vnet.ibm.com>
Cc: Dave Hansen <dave@sr71.net>,
Nathan Fontenot <nfont@linux.vnet.ibm.com>,
Cody P Schafer <cody@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Yinghai Lu <yinghai@kernel.org>,
Wanpeng Li <liwanp@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/7] drivers: base: move mutex lock out of add_memory_section()
Date: Wed, 21 Aug 2013 11:50:51 -0700 [thread overview]
Message-ID: <20130821185051.GA11574@kroah.com> (raw)
In-Reply-To: <20130820172445.GE4151@medulla.variantweb.net>
On Tue, Aug 20, 2013 at 12:24:45PM -0500, Seth Jennings wrote:
> Gah! Forgot the cover letter.
No worries, I barely read them anyway :)
> This patchset just seeks to clean up and refactor some things in
> memory.c for better understanding and possibly better performance due do
> a decrease in mutex acquisitions and refcount churn at boot time. No
> functional change is intended by this set!
All looks good, thanks for breaking it up into reviewable patches. Now
applied.
greg k-h
next prev parent reply other threads:[~2013-08-21 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1377018783-26756-1-git-send-email-sjenning@linux.vnet.ibm.com>
[not found] ` <1377018783-26756-7-git-send-email-sjenning@linux.vnet.ibm.com>
2013-08-22 8:20 ` [PATCH 7/7] drivers: base: refactor add_memory_section() to add_memory_block() Yasuaki Ishimatsu
2013-08-22 8:30 ` Yasuaki Ishimatsu
[not found] ` <20130820172445.GE4151@medulla.variantweb.net>
2013-08-21 18:50 ` Greg Kroah-Hartman [this message]
2013-08-22 8:44 ` [PATCH 1/7] drivers: base: move mutex lock out of add_memory_section() Yasuaki Ishimatsu
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=20130821185051.GA11574@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=cody@linux.vnet.ibm.com \
--cc=dave@sr71.net \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=liwanp@linux.vnet.ibm.com \
--cc=nfont@linux.vnet.ibm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=sjenning@linux.vnet.ibm.com \
--cc=yinghai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox