linux-kernel - Re: [GIT PULL v2] Update LZO compression

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20121003143200.69a50aad.akpm@linux-foundation.org>
Date:	Wed, 3 Oct 2012 14:32:00 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	richard -rw- weinberger <richard.weinberger@...il.com>,
	"Markus F.X.J. Oberhumer" <markus@...rhumer.com>,
	linux-kernel@...r.kernel.org, chris.mason@...ionio.com,
	linux-btrfs@...r.kernel.org, Nitin Gupta <ngupta@...are.org>,
	Johannes Stezenbach <js@...21.net>
Subject: Re: [GIT PULL v2] Update LZO compression

On Wed, 3 Oct 2012 23:19:04 +0200
Andi Kleen <andi@...stfloor.org> 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 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 style." to indicate a rigorous code review!

That's the problem with the git presentation: hardly anyone reads the
patches and there is no patch for a reviewer to reply to.

So please send the patches out for review.  One at a time, via email.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/