Messages in this thread | | | Date | Thu, 2 Jun 2005 07:32:19 -0500 | From | Michael Halcrow <> | Subject | Re: [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?
Thanks, Mike - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |