linux-kernel - Re: Subject: [PATCH 00/16] Squashfs: compressed read-only filesystem

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]

Date:	Wed, 22 Oct 2008 00:15:44 +0100
From:	Phillip Lougher <phillip@...gher.demon.co.uk>
To:	Alex Riesen <raa.lkml@...il.com>
CC:	akpm@...ux-foundation.org, linux-embedded@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
	tim.bird@...sony.com
Subject: Re: Subject: [PATCH 00/16] Squashfs: compressed read-only filesystem

Alex Riesen wrote:
> 2008/10/17 Phillip Lougher <phillip@...gher.demon.co.uk>:
>> There are 16 patches in the patch set, and the patches are against the
>> latest linux-next tree (linux 2.6.27-next-20081016).
> 
> You better don't base anything off linux-next. These are not stable: there
> can be even something in the tree you mentioned which will never end
> up in the mainline and if your patches depend on it they wont apply to
> something like v2.6.26.2.

Definately, there's some d_obtain_alias stuff in linux-next which has 
been there since linux-2.6.27-rc4-next.  I thought it would make it into 
the final 2.6.27 but it didn't.

I thought linux-next *was* the tree that new patches should be based 
off.  However, the relationship between linux-2.6.git, linux-next.git, 
and the  -mm patch series seems to be a little vague to me, not to 
mention where the linux-staging tree fits into all this.

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