Re: [PATCH 3/11] eCryptfs: read_write.c routines

On Mon, 17 Sep 2007 16:46:32 -0500 Michael Halcrow <[email protected]> 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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH 0/11] eCryptfs: Introduce persistent lower files for each eCryptfs inode
    • From: Michael Halcrow <[email protected]>
  • [PATCH 3/11] eCryptfs: read_write.c routines
    • From: Michael Halcrow <[email protected]>

• Prev by Date: Re: 2.6.23-rc6-mm1 powerpc - kgdb is broken
• Next by Date: Re: [PATCH 4/4] [-mm patch] Add a prefix "VMCOREINFO_" to the vmcoreinfo macros.
• Previous by thread: [PATCH 3/11] eCryptfs: read_write.c routines
• Next by thread: Re: [PATCH 3/11] eCryptfs: read_write.c routines
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]