From: Johannes Weiner <hannes@cmpxchg.org>
To: Chanho Min <chanho.min@lge.com>
Cc: 'Zhang Yanfei' <zhangyanfei@cn.fujitsu.com>,
'Andrew Morton' <akpm@linux-foundation.org>,
iamjoonsoo.kim@lge.com, linux-kernel@vger.kernel.org,
'Linux MM' <linux-mm@kvack.org>, 'Mel Gorman' <mgorman@suse.de>
Subject: Re: [PATCH 0/3] mm, vmalloc: cleanup for vmap block
Date: Thu, 20 Jun 2013 02:38:17 -0400 [thread overview]
Message-ID: <20130620063817.GA1079@cmpxchg.org> (raw)
In-Reply-To: <006801ce6577$a50317c0$ef094740$@min@lge.com>
On Mon, Jun 10, 2013 at 10:12:57AM +0900, Chanho Min wrote:
> > This patchset is a cleanup for vmap block. And similar/same
> > patches has been submitted before:
> > - Johannes Weiner's patch: https://lkml.org/lkml/2011/4/14/619
> > - Chanho Min's patch: https://lkml.org/lkml/2013/2/6/810
>
> This is exactly the same patch as mine. The previous two patches are
> should be concluded.
Ping. This code is identical, it should credit Chanho as the original
author. And I agree that the patches should be folded into one patch.
Thanks!
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Weiner <hannes@cmpxchg.org>
To: Chanho Min <chanho.min@lge.com>
Cc: "'Zhang Yanfei'" <zhangyanfei@cn.fujitsu.com>,
"'Andrew Morton'" <akpm@linux-foundation.org>,
iamjoonsoo.kim@lge.com, linux-kernel@vger.kernel.org,
"'Linux MM'" <linux-mm@kvack.org>,
"'Mel Gorman'" <mgorman@suse.de>
Subject: Re: [PATCH 0/3] mm, vmalloc: cleanup for vmap block
Date: Thu, 20 Jun 2013 02:38:17 -0400 [thread overview]
Message-ID: <20130620063817.GA1079@cmpxchg.org> (raw)
In-Reply-To: <006801ce6577$a50317c0$ef094740$@min@lge.com>
On Mon, Jun 10, 2013 at 10:12:57AM +0900, Chanho Min wrote:
> > This patchset is a cleanup for vmap block. And similar/same
> > patches has been submitted before:
> > - Johannes Weiner's patch: https://lkml.org/lkml/2011/4/14/619
> > - Chanho Min's patch: https://lkml.org/lkml/2013/2/6/810
>
> This is exactly the same patch as mine. The previous two patches are
> should be concluded.
Ping. This code is identical, it should credit Chanho as the original
author. And I agree that the patches should be folded into one patch.
Thanks!
next prev parent reply other threads:[~2013-06-20 6:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 9:51 [PATCH 0/3] mm, vmalloc: cleanup for vmap block Zhang Yanfei
2013-06-07 9:51 ` Zhang Yanfei
2013-06-07 9:53 ` [PATCH 1/3] mm, vmalloc: Remove dead code in vb_alloc Zhang Yanfei
2013-06-07 9:53 ` Zhang Yanfei
2013-06-07 9:54 ` [PATCH 2/3] mm, vmalloc: Remove unused purge_fragmented_blocks_thiscpu Zhang Yanfei
2013-06-07 9:54 ` Zhang Yanfei
2013-06-07 9:55 ` [PATCH 3/3] mm, vmalloc: Remove alloc_map from vmap_block Zhang Yanfei
2013-06-07 9:55 ` Zhang Yanfei
2013-06-10 1:12 ` [PATCH 0/3] mm, vmalloc: cleanup for vmap block Chanho Min
2013-06-10 1:12 ` Chanho Min
2013-06-20 6:38 ` Johannes Weiner [this message]
2013-06-20 6:38 ` Johannes Weiner
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=20130620063817.GA1079@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=chanho.min@lge.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=zhangyanfei@cn.fujitsu.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.