| 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: <20131109083215.GA12574@infradead.org> Date: Sat, 9 Nov 2013 00:32:15 -0800 From: Christoph Hellwig <hch@...radead.org> To: "Eric W. Biederman" <ebiederm@...ssion.com> Cc: Christoph Hellwig <hch@...radead.org>, Stephen Rothwell <sfr@...b.auug.org.au>, Al Viro <viro@...iv.linux.org.uk>, linux-next@...r.kernel.org, linux-kernel@...r.kernel.org, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: linux-next: build failure after merge of the userns tree On Fri, Nov 08, 2013 at 02:50:42PM -0800, Eric W. Biederman wrote: > Al was watching the conversation so I assumed that no answer to that > request was sufficient to take these patches in my tree. > > I fully intend to take responsibility for these patches and work through > whatever issues they have, and I intend to send Linus my pull request. > As such dropping the userns tree from linux-next seems inappropriate. > It's not. Really, if you do touch core code and do not get a maintainer respone it surely does not mean you can merge it through your tree. It usually either means this stuff is so bad that it's not even worth responding to or that the maintainer and core revierers of the area are busy. In this case it's probably a combination of both. > Eric ---end quoted text--- -- 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