public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Minchan Kim <minchan.kim@gmail.com>,
	Nitin Gupta <ngupta@vflare.org>, Greg KH <greg@kroah.com>,
	Ed Tomlinson <edt@aei.ca>,
	Hugh Dickins <hugh.dickins@tiscali.co.uk>, Cyp <cyp561@gmail.com>,
	driverdev <devel@driverdev.osuosl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] Support generic I/O requests
Date: Sat, 05 Jun 2010 11:28:38 +0300	[thread overview]
Message-ID: <4C0A0AB6.20206@cs.helsinki.fi> (raw)
In-Reply-To: <20100604121957.d9bc55ae.akpm@linux-foundation.org>

Andrew Morton wrote:
>> I thought zram is related to memory management a little bit.
>>
>> What's the criteria?
> 
> Yes, and this is something which bothers me a bit about the -staging
> process.  Code gets in there largely under the radar of the people who
> work in that area.  It gets "matured" for a while and the developer
> thinks it's all ready to go into "mainline" and ....  then what? 
> Someone needs to yank the code out of -staging and tell the interested
> parties "hey, look at this".  And at this stage, they might say "hell
> no", or request large changes and the developer who thought everything
> was all ready to go would be justifiably upset.

Yeah, that's what I assumed would happen here. When the code in -staging 
is "good enough", Nitin would submit squashed patches for inclusion 
review and when everyone is happy, we'd merge the code including full 
history from -staging.

Btw, ramzswap and zram have been discussed openly on LKML. I guess Nitin 
should have CC'd linux-mm as well for you to see it Andrew?

			Pekka

  reply	other threads:[~2010-06-05  8:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01  8:01 [PATCH 0/4] zram: generic RAM based compressed R/W block devices (v2) Nitin Gupta
2010-06-01  8:01 ` [PATCH 1/4] Support generic I/O requests Nitin Gupta
2010-06-02  6:20   ` Minchan Kim
2010-06-02  7:36     ` Nitin Gupta
2010-06-04 19:19     ` Andrew Morton
2010-06-05  8:28       ` Pekka Enberg [this message]
2010-06-05  8:36         ` Pekka Enberg
2010-06-05  8:35       ` Pekka Enberg
2010-06-05 13:15         ` Nitin Gupta
2010-06-06 23:32         ` Minchan Kim
2010-06-07  5:35           ` Pekka Enberg
2010-06-04 19:10   ` Andrew Morton
2010-06-05  7:44     ` Nitin Gupta
2010-06-01  8:01 ` [PATCH 2/4] Rename ramzswap files to zram Nitin Gupta
2010-06-04 19:32   ` Andrew Morton
2010-06-04 21:07     ` Greg KH
2010-06-05  7:00     ` Nitin Gupta
2010-06-01  8:01 ` [PATCH 3/4] Rename ramzswap to zram in code Nitin Gupta
2010-06-01  8:01 ` [PATCH 4/4] Rename ramzswap to zram in documentation Nitin Gupta
2010-06-01 10:25 ` [PATCH 0/4] zram: generic RAM based compressed R/W block devices (v2) Pekka Enberg

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=4C0A0AB6.20206@cs.helsinki.fi \
    --to=penberg@cs.helsinki.fi \
    --cc=akpm@linux-foundation.org \
    --cc=cyp561@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=edt@aei.ca \
    --cc=greg@kroah.com \
    --cc=hugh.dickins@tiscali.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minchan.kim@gmail.com \
    --cc=ngupta@vflare.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