[lkml]   [2005]   [Jun]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 1/3] eCryptfs: eCryptfs kernel module
On Thu, Jun 02, 2005 at 03:33:58AM -0400, James Morris wrote:
> Break up your patch and send it in logical chunks, so it can be
> reviewed easily.

In discussions with some developers from JFS and CIFS, it was
suggested that the best thing would be to submit one patch with the
whole contents of the fs/ecryptfs directory, since it is a new
filesystem with no modifications to existing code. What sort of
logical chunks would you consider to be appropriate? Separate patches
for each file (inode.c, file.c, super.c, etc.), which represent sets
of functions for each major VFS object?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-06-02 14:39    [W:0.063 / U:8.428 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site