From: Minchan Kim <minchan@kernel.org>
Cc: Seth Jennings <sjenning@linux.vnet.ibm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Nitin Gupta <ngupta@vflare.org>
Subject: Re: [PATCH] zsmalloc: use unsigned long instead of void *
Date: Wed, 23 May 2012 10:47:14 +0900 [thread overview]
Message-ID: <4FBC41A2.1080402@kernel.org> (raw)
In-Reply-To: <4FBC2916.5000305@kernel.org>
On 05/23/2012 09:02 AM, Minchan Kim wrote:
> Maybe I will resend next spin based on v3.4 today
> I hope it doesn't hurt you.
I didn't based v2 patches on v3.4 because mainline tree doesn't have lots of staging patchset.
So it's not a good idea to apply staging patchset in mainline. I believe linux-next is good candidate
for it so I sent v2 patches against next-20120522.
Thanks.
--
Kind regards,
Minchan Kim
--
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 internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Minchan Kim <minchan@kernel.org>
To: undisclosed-recipients:;
Cc: Seth Jennings <sjenning@linux.vnet.ibm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Nitin Gupta <ngupta@vflare.org>
Subject: Re: [PATCH] zsmalloc: use unsigned long instead of void *
Date: Wed, 23 May 2012 10:47:14 +0900 [thread overview]
Message-ID: <4FBC41A2.1080402@kernel.org> (raw)
In-Reply-To: <4FBC2916.5000305@kernel.org>
On 05/23/2012 09:02 AM, Minchan Kim wrote:
> Maybe I will resend next spin based on v3.4 today
> I hope it doesn't hurt you.
I didn't based v2 patches on v3.4 because mainline tree doesn't have lots of staging patchset.
So it's not a good idea to apply staging patchset in mainline. I believe linux-next is good candidate
for it so I sent v2 patches against next-20120522.
Thanks.
--
Kind regards,
Minchan Kim
next prev parent reply other threads:[~2012-05-23 1:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 2:23 [PATCH] zsmalloc: use unsigned long instead of void * Minchan Kim
2012-05-21 2:23 ` Minchan Kim
2012-05-21 14:19 ` Seth Jennings
2012-05-21 14:19 ` Seth Jennings
2012-05-21 15:04 ` Dan Magenheimer
2012-05-21 15:04 ` Dan Magenheimer
2012-05-22 13:42 ` Seth Jennings
2012-05-22 13:42 ` Seth Jennings
2012-05-22 18:31 ` Konrad Rzeszutek Wilk
2012-05-22 18:31 ` Konrad Rzeszutek Wilk
2012-05-22 18:45 ` Seth Jennings
2012-05-22 18:45 ` Seth Jennings
2012-05-23 0:02 ` Minchan Kim
2012-05-23 0:02 ` Minchan Kim
2012-05-23 1:47 ` Minchan Kim [this message]
2012-05-23 1:47 ` Minchan Kim
2012-05-23 5:55 ` Greg Kroah-Hartman
2012-05-23 5:55 ` Greg Kroah-Hartman
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=4FBC41A2.1080402@kernel.org \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dan.magenheimer@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ngupta@vflare.org \
--cc=sjenning@linux.vnet.ibm.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.