linux-kernel - Re: [GIT PULL] bzip2/lzma kernel 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 for Android: free password hash cracker in your pocket

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

Message-ID: <49693E70.4050303@zytor.com>
Date:	Sat, 10 Jan 2009 16:33:52 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Alain Knaff <alain@...ff.lu>
CC:	Sam Ravnborg <sam@...nborg.org>,
	Russell King <rmk@....linux.org.uk>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] bzip2/lzma kernel compression

Alain Knaff wrote:
> 
> But now I am curious how this will evolve from here. I suppose it will
> soon appear in one of the patch-2.6.28-gitxy.gz under
> ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots , and then in an
> 2.6.29-rcx etc.
> Or are there some more other steps involved in between?
> 

Well, Linus opted not to merge it for 2.6.29-rc1, which means it is dead
for this merge cycle.  This gives us a couple of options, with the aim
to get it merged into 2.6.30:

- We can continue to carry it in the -tip tree, which also means it will
  be in the linux-next tree.
- We can push it to Andrew Morton for the -mm tree.
- Sam could take it in his kbuild tree.

Out of these, I think the kbuild tree is entirely inappropriate.  The
selection of the other two is mostly a matter of testing, and which way
will be easier to add the ARM code and other arch support.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
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/