> > > - Post the entire patch series to lkml for review (I'd like a cc please)
> >
> > Already happened, multiple people reviewed and tested.
>
> um, I would not consider "Looks ok to me from a quick look." and "I
> couldn't tell from the github view, but I assume you follow standard
> coding sty
On Wed, 3 Oct 2012 23:19:04 +0200
Andi Kleen wrote:
> > 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)
>
> Already happened, multiple people reviewed and tested.
um, I would not
> 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)
Already happened, multiple people reviewed and tested.
This was just the patch ping.
-Andi
--
a...@linux.intel.com -- Speaking for mys
On Wed, 3 Oct 2012 12:48:46 +0200
richard -rw- weinberger 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/Testi
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,
CC'in akpm.
On Wed, Oct 3, 2012 at 12:34 PM, Markus F.X.J. Oberhumer
wrote:
> 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 preferre
On Tue, Aug 21, 2012 at 05:21:50PM +0200, Markus F.X.J. Oberhumer wrote:
> as suggested on the mailing list I have converted the updated LZO
> code into git, so please pull my "lzo-update" branch from
...
> [ Changes in v2: Optimize code for CPUs with inefficient unaligned
> access => significant
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
