linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Markus F.X.J. Oberhumer" <markus@oberhumer.com>
To: linux-kernel@vger.kernel.org
Cc: Andi Kleen <andi@firstfloor.org>,
	chris.mason@fusionio.com, linux-btrfs@vger.kernel.org,
	Nitin Gupta <ngupta@vflare.org>,
	richard -rw- weinberger <richard.weinberger@gmail.com>,
	Johannes Stezenbach <js@sig21.net>
Subject: Re: [GIT PULL v2] Update LZO compression
Date: Wed, 03 Oct 2012 12:34:34 +0200	[thread overview]
Message-ID: <506C14BA.70006@oberhumer.com> (raw)
In-Reply-To: <5033A78E.3080703@oberhumer.com>

Hi all,

is there some official maintainer who feels responsible for
pushing the LZO update to Linus?

Otherwise I also could issue a pull-request on github, but somehow I
don't think that this is the preferred workflow.

Cheers,
Markus

On 2012-08-21 17:21, Markus F.X.J. Oberhumer wrote:
> Hi all,
> 
> as suggested on the mailing list I have converted the updated LZO
> code into git, so please pull my "lzo-update" branch from
> 
>   git://github.com/markus-oberhumer/linux.git lzo-update
> 
> You can browse the branch at
> 
>   https://github.com/markus-oberhumer/linux/compare/lzo-update
> 
> I'd ask some official kernel maintainer for review and to push this into
> linux-next so that it will hopefully land in the 3.7 release.
> 
> Share and enjoy,
> Markus
> 
> Signed-off-by: Markus F.X.J. Oberhumer <markus@oberhumer.com>
> 
> 
> [ Changes in v2: Optimize code for CPUs with inefficient unaligned
>   access => significant speed increase on ARM ]
> 
> 
> On 2012-07-16 20:30, Markus F.X.J. Oberhumer wrote:
>> 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.
>>
>> Share and enjoy,
>> Markus
>>
>> Signed-off-by: Markus F.X.J. Oberhumer" <markus@oberhumer.com>

-- 
Markus Oberhumer, <markus@oberhumer.com>, http://www.oberhumer.com/

  parent reply	other threads:[~2012-10-03 10:54 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 [this message]
2012-10-03 10:48   ` richard -rw- weinberger
2012-10-03 21:01     ` Andrew Morton
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=506C14BA.70006@oberhumer.com \
    --to=markus@oberhumer.com \
    --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=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).