From: Greg KH <gregkh@linuxfoundation.org>
To: Nitin Gupta <ngupta@vflare.org>
Cc: Olav Haugan <ohaugan@codeaurora.org>,
Seth Jennings <sjenning@linux.vnet.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Minchan Kim <minchan@kernel.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] staging: zsmalloc: Ensure handle is never 0 on success
Date: Wed, 6 Nov 2013 19:05:11 -0800 [thread overview]
Message-ID: <20131107030511.GC8482@kroah.com> (raw)
In-Reply-To: <CAPkvG_fgkqeQt3=eqnDM7bWQXdeeybRULiU2MdNh5KF1KoeRFw@mail.gmail.com>
On Wed, Nov 06, 2013 at 03:46:19PM -0800, Nitin Gupta wrote:
> I'm getting really tired of them hanging around in here for many years
> > now...
> >
>
> Minchan has tried many times to promote zram out of staging. This was
> his most recent attempt:
>
> https://lkml.org/lkml/2013/8/21/54
>
> There he provided arguments for zram inclusion, how it can help in
> situations where zswap can't and why generalizing /dev/ramX would
> not be a great idea. So, cannot say why it wasn't picked up
> for inclusion at that time.
>
> > Should I just remove them if no one is working on getting them merged
> > "properly"?
> >
>
> Please refer the mail thread (link above) and see Minchan's
> justifications for zram.
> If they don't sound convincing enough then please remove zram+zsmalloc
> from staging.
You don't need to be convincing me, you need to be convincing the
maintainers of the area of the kernel you are working with.
And since the last time you all tried to get this merged was back in
August, I'm feeling that you all have given up, so it needs to be
deleted. I'll go do that for 3.14, and if someone wants to pick it up
and merge it properly, they can easily revert it.
thanks,
greg k-h
next prev parent reply other threads:[~2013-11-07 3:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 0:54 [PATCH] staging: zsmalloc: Ensure handle is never 0 on success Olav Haugan
2013-11-06 1:17 ` David Cohen
2013-11-06 20:56 ` Nitin Gupta
2013-11-06 23:46 ` Olav Haugan
2013-11-06 1:56 ` Greg KH
2013-11-06 21:09 ` Nitin Gupta
2013-11-06 22:10 ` Greg KH
2013-11-06 23:46 ` Nitin Gupta
2013-11-07 3:05 ` Greg KH [this message]
2013-11-07 0:00 ` Olav Haugan
2013-11-07 3:06 ` Greg KH
2013-11-07 22:57 ` Olav Haugan
-- strict thread matches above, loose matches on Subject: below --
2013-11-07 7:04 Minchan Kim
2013-11-07 17:06 ` Luigi Semenzato
2013-11-07 17:36 ` Luigi Semenzato
2013-11-08 2:02 ` Greg KH
2013-11-07 17:10 ` Rik van Riel
2013-11-08 10:44 ` Bob Liu
2013-11-12 15:41 ` Minchan Kim
2013-11-13 2:42 ` Greg KH
2013-11-13 6:24 ` Nitin Gupta
2013-11-14 4:00 ` Hugh Dickins
2013-11-14 16:21 ` Seth Jennings
2013-11-15 0:47 ` Bob Liu
2013-11-15 0:31 ` Minchan Kim
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=20131107030511.GC8482@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=ohaugan@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox