public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Nitin Gupta" <nitingupta910@gmail.com>
Cc: "Adrian Bunk" <bunk@stusta.de>,
	"Richard Purdie" <rpurdie@openedhand.com>,
	"Daniel Hazelton" <dhazelton@enter.net>,
	LKML <linux-kernel@vger.kernel.org>,
	"Hugh Dickins" <hugh@veritas.com>,
	"Nick Piggin" <nickpiggin@yahoo.com.au>,
	"David Woodhouse" <dwmw2@infradead.org>
Subject: Re: [PATCH -mm 0/5] LZO and swap write failure patches for -mm
Date: Mon, 4 Jun 2007 22:50:38 -0700	[thread overview]
Message-ID: <20070604225038.9973226b.akpm@linux-foundation.org> (raw)
In-Reply-To: <4cefeab80706042230u1fc7f485j30cea371d1d3117a@mail.gmail.com>

On Tue, 5 Jun 2007 11:00:05 +0530 "Nitin Gupta" <nitingupta910@gmail.com> wrote:

> Andrew, Andrian,
> 
> If you really have the opinion of not going for major cleanups,
> optimizations outside of original LZO code (basically a fork), then
> there is no point in me continuing this work.

err, my LZO attention span ran out 200 emails ago.

> If you think otherwise, please let me know and I will post a newer
> version with improvements from all these feedback I got.
> 

I'd say go with the cleanups.  The code I've seen is going to be quite
unmaintainable by any kernel developer.

Any fixes which come from upstream can be trivially applied by taking the
diffs against the version of upstream we started with and manually applying
them to our version.  If the diffs are too large and complex for that then
a) we shouldn't be merging the code in its current state anyway and b) with
the code as-is we couldn't effectively review or changelog those diffs, so
we shouldn't apply them.

So just fork it and freeze it.

(And please never top-post when working with kernel people).

  reply	other threads:[~2007-06-05  5:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-04 15:36 [PATCH -mm 0/5] LZO and swap write failure patches for -mm Richard Purdie
2007-06-04 16:14 ` Daniel Hazelton
2007-06-04 16:52   ` Richard Purdie
2007-06-04 17:37     ` Daniel Hazelton
2007-06-04 18:34       ` Nitin Gupta
2007-06-04 20:45       ` Richard Purdie
2007-06-04 22:13         ` Daniel Hazelton
2007-06-04 18:26     ` Nitin Gupta
2007-06-04 20:06       ` Adrian Bunk
2007-06-05  5:30         ` Nitin Gupta
2007-06-05  5:50           ` Andrew Morton [this message]
2007-06-05  8:56             ` Richard Purdie
2007-06-04 20:58       ` Richard Purdie
2007-06-05  6:15         ` Christoph Hellwig

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=20070604225038.9973226b.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bunk@stusta.de \
    --cc=dhazelton@enter.net \
    --cc=dwmw2@infradead.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=nitingupta910@gmail.com \
    --cc=rpurdie@openedhand.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