| 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
| ||
|
Message-Id: <20070307004919.b5b8b7da.akpm@linux-foundation.org> Date: Wed, 7 Mar 2007 00:49:19 -0800 From: Andrew Morton <akpm@...ux-foundation.org> To: Sébastien Dugué <sebastien.dugue@...l.net> Cc: linux-kernel@...r.kernel.org Subject: Re: 2.6.21-rc2-mm2 On Wed, 7 Mar 2007 09:39:48 +0100 Sébastien Dugué <sebastien.dugue@...l.net> wrote: > > Hi Andrew, > > On Tue, 6 Mar 2007 00:44:08 -0800 Andrew Morton <akpm@...ux-foundation.org> wrote: > > > > > Temporarily at > > > > http://userweb.kernel.org/~akpm/2.6.21-rc2-mm2/ > > > > Will appear later at > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc2/2.6.20-rc2-mm2/ > > > > > > - git-block.patch is having problems which are getting in the way - it has > > been dropped. > > > > - As a consequence all the AIO patches were dropped > > > > Why? The aio notification and listio patches have nothing to do with > git-block.patch. Yes, I could have retained those with a little bit of jiggling. But... > If you think those patches will be rendered obsolete by the new > syslet/fibril/whatever approach, then fine. Until this is sorted out I don't think we can add new core AIO code. Particularly not new syscalls. > Otherwise do you expect me to > resubmit? Is OK for now, I think. - 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/
Powered by blists - more mailing lists