linux-kernel - Re: [PATCH 00/13] Use struct path in struct nameidata

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]

Message-ID: <20071023084305.GJ17591@hasse.suse.de>
Date:	Tue, 23 Oct 2007 10:43:05 +0200
From:	Jan Blunck <jblunck@...e.de>
To:	Bharata B Rao <bharata@...ux.vnet.ibm.com>
Cc:	Christoph Hellwig <hch@....de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Andreas Gruenbacher <agruen@...e.de>, viro@...iv.linux.org.uk,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/13] Use struct path in struct nameidata

On Tue, Oct 23, Bharata B Rao wrote:

> On Mon, Oct 22, 2007 at 03:57:58PM +0200, Christoph Hellwig wrote:
> > 
> > Any reason we've got this patchset posted by three people now? :)
> 
> Two reasons actually !
> 
> - The set of patches posted by Jan last was on 2.6.23-rc8-mm1. So I
> thought let me help Andrew a bit by making them available on latest
> -mm :) And I didn't know that these were already under consideration
> by Andrew.

And they have been ported to 2.6.23-mm1 since the day it came out ...

> - The set of patches posted by Jan didn't even pass compile test for me.
> So I made sure that the patches compiled and worked on x86, x86_64 and powerpc.

And I merged your feedback already in ...

The thing is: how do we keep going from here? Do you want to send my patches
in the future or are you going to ask me before sending things out? We don't
need to duplicate the work here. I already put my quilt stack into a public
place for you to work on them but I don't like the way this is going on at the
moment.
-
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/