From: Christoph Lameter <cl@linux.com>
To: jovi zhang <bookjovi@gmail.com>
Cc: Jesper Juhl <jj@chaosbits.net>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Minchan Kim <minchan.kim@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Paul Menage <menage@google.com>, Li Zefan <lizf@cn.fujitsu.com>,
containers@lists.linux-foundation.org
Subject: Re: [PATCH] cgroup: Avoid a memset by using vzalloc
Date: Wed, 3 Nov 2010 10:31:01 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1011031030150.11625@router.home> (raw)
In-Reply-To: <AANLkTinhAQ7mNQWtjWCOWEHHwgUf+BynMM7jnVBMG32-@mail.gmail.com>
On Wed, 3 Nov 2010, jovi zhang wrote:
> On Wed, Nov 3, 2010 at 10:38 PM, Christoph Lameter <cl@linux.com> wrote:
> > Could we avoid this painful exercise with a "semantic patch"?
> Can we make a grep script to walk all files to find vzalloc usage like this?
> No need to send patch mail one by one like this.
Please use spatch. See http://lwn.net/Articles/315686/
--
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/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-11-03 15:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 21:35 Jesper Juhl
2010-10-30 23:34 ` Minchan Kim
2010-10-31 17:33 ` Balbir Singh
2010-11-01 5:40 ` Jesper Juhl
2010-11-03 14:38 ` Christoph Lameter
2010-11-03 15:20 ` jovi zhang
2010-11-03 15:31 ` Christoph Lameter [this message]
2010-11-03 15:48 ` Joe Perches
2010-11-03 16:10 ` Christoph Lameter
2010-11-04 21:43 ` Jesper Juhl
2010-11-05 3:07 ` [PATCH 00/49] Use vzalloc not vmalloc/kmemset Joe Perches
2010-11-05 3:08 ` [PATCH 44/49] mm: Use vzalloc Joe Perches
2010-11-03 16:37 ` [PATCH] cgroup: Avoid a memset by using vzalloc Américo Wang
2010-11-01 22:00 ` 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=alpine.DEB.2.00.1011031030150.11625@router.home \
--to=cl@linux.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=bookjovi@gmail.com \
--cc=containers@lists.linux-foundation.org \
--cc=jj@chaosbits.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=minchan.kim@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox