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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 20 Apr 2007 01:58:38 -0700 (PDT) From: David Miller <davem@...emloft.net> To: dhowells@...hat.com Cc: ebiederm@...ssion.com, akpm@...l.org, containers@...ts.osdl.org, oleg@...sign.ru, hch@...radead.org, linux-kernel@...r.kernel.org, netdev@...r.kernel.org Subject: Re: Getting the new RxRPC patches upstream From: David Howells <dhowells@...hat.com> Date: Fri, 20 Apr 2007 09:02:07 +0100 > David Miller <davem@...emloft.net> wrote: > > > I applied already the patches I thought were appropriate, > > you had some crypto layer changes that you need to work > > out with Herbert Xu before the rest can be applied. > > Should the rest of it go via Andrew's tree then? Now that Herbert cleared up the crypto layer issues the only problem left is that there are generic changes in there which are not strictly networking but which your subsequent networking changes depend upon. This is a mess, and makes merging your work into the net-2.6.22 tree more difficult. Is it possible for your changes to be purely networking and not need those changes outside of the networking? I guess one of them was just a symbol export which I could add to the net-2.6.22 tree, but weren't there some more involved non-networking bits in there? - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists