From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [PATCH 3/11] eCryptfs: read_write.c routines Date: Wed, 19 Sep 2007 22:25:05 -0700 Message-ID: <20070919222505.28a238b0.akpm@linux-foundation.org> References: <20070917214436.GH13679@halcrow.austin.ibm.com> <20070917214632.GK13679@halcrow.austin.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, ecryptfs-devel@lists.sourceforge.net To: Michael Halcrow Return-path: In-Reply-To: <20070917214632.GK13679@halcrow.austin.ibm.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ecryptfs-devel-bounces@lists.sourceforge.net Errors-To: ecryptfs-devel-bounces@lists.sourceforge.net List-Id: linux-fsdevel.vger.kernel.org On Mon, 17 Sep 2007 16:46:32 -0500 Michael Halcrow wrote: > +/** > + * ecryptfs_write_lower > + * @ecryptfs_inode: The eCryptfs inode > + * @data: Data to write > + * @offset: Byte offset in the lower file to which to write the data > + * @size: Number of bytes from @data to write at @offset in the lower > + * file > + * > + * Write data to the lower file. > + * > + * Returns zero on success; non-zero on error > + */ That might come out looking odd in the kernel doc? Normally the documentation would start out with +/** + * ecryptfs_write_lower - write data to the lower file ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/