linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: "Markus F.X.J. Oberhumer" <markus@oberhumer.com>,
	linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
	chris.mason@fusionio.com, linux-btrfs@vger.kernel.org,
	Nitin Gupta <ngupta@vflare.org>,
	Johannes Stezenbach <js@sig21.net>
Subject: Re: [GIT PULL v2] Update LZO compression
Date: Wed, 3 Oct 2012 14:01:36 -0700	[thread overview]
Message-ID: <20121003140136.f2b071df.akpm@linux-foundation.org> (raw)
In-Reply-To: <CAFLxGvw3OqOb0UVhjtwC+CD+wtubH-O1FM7=fYFT8ztWPVPd6w@mail.gmail.com>

On Wed, 3 Oct 2012 12:48:46 +0200
richard -rw- weinberger <richard.weinberger@gmail.com> wrote:

> CC'in akpm.

Thanks.

> >>> Hi all,
> >>>
> >>> I finally have prepared a small package that updates the LZO version
> >>> in the Linux kernel. Please get it from:
> >>>
> >>> http://www.oberhumer.com/opensource/lzo/download/Testing/linux-kernel-lzo-20120716.tar.gz
> >>>
> >>> As stated in the README this version is significantly faster (typically more
> >>> than 2 times faster!) than the current version, has been thoroughly tested on
> >>> x86_64/i386/powerpc platforms and is intended to get included into the
> >>> official Linux 3.6 or 3.7 release.
> >>>
> >>> I encourage all compression users to test and benchmark this new version,
> >>> and I also would ask some official LZO maintainer to convert the updated
> >>> source files into a GIT commit and possibly push it to Linus or linux-next.

No, lib/lzo has no identifiable maintainer.  I suggest you proceed as
follows:

- Post the entire patch series to lkml for review (I'd like a cc please)

- After that process has played out, ask Stephen to add this git tree
  to linux-next.

- After that process has played out, ask Linus to pull the tree
  during a merge window.

I haven't actually looked at the patches yet, but if they are as
extensive as they sound, it would be appropriate for you become the
formal maintainer of lib/lzo.


  reply	other threads:[~2012-10-03 21:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-21 15:21 [GIT PULL v2] Update LZO compression Markus F.X.J. Oberhumer
2012-08-22 10:34 ` Johannes Stezenbach
2012-10-03 10:34 ` Markus F.X.J. Oberhumer
2012-10-03 10:48   ` richard -rw- weinberger
2012-10-03 21:01     ` Andrew Morton [this message]
2012-10-03 21:19       ` Andi Kleen
2012-10-03 21:32         ` Andrew Morton
2012-10-04  1:51           ` Andi Kleen

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=20121003140136.f2b071df.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=chris.mason@fusionio.com \
    --cc=js@sig21.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@oberhumer.com \
    --cc=ngupta@vflare.org \
    --cc=richard.weinberger@gmail.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;
as well as URLs for NNTP newsgroup(s).