linux-kernel - Re: [PATCH] ecryptfs: fix spelling mistakes

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] [day] [month] [year] [list]

Message-ID: <5768078C.4080701@canonical.com>
Date:	Mon, 20 Jun 2016 10:11:08 -0500
From:	Tyler Hicks <tyhicks@...onical.com>
To:	Chris J Arges <chris.j.arges@...onical.com>
Cc:	ecryptfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ecryptfs: fix spelling mistakes

On 06/09/2016 03:31 PM, Chris J Arges wrote:
> Noticed some minor spelling errors when looking through the code.
> 
> Signed-off-by: Chris J Arges <chris.j.arges@...onical.com>

Hey Chris - thanks for these fixups. The first two hunks
(respresentation -> representation) were already fixed by an older patch
that is pending in the eCryptfs next branch. I dropped those hunks,
added my S-o-b, and pushed this patch to the eCryptfs next branch.

Tyler

> ---
>  fs/ecryptfs/crypto.c | 8 ++++----
>  fs/ecryptfs/file.c   | 4 ++--
>  2 files changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/fs/ecryptfs/crypto.c b/fs/ecryptfs/crypto.c
> index 0d8eb34..e5e29f8 100644
> --- a/fs/ecryptfs/crypto.c
> +++ b/fs/ecryptfs/crypto.c
> @@ -45,7 +45,7 @@
>   * ecryptfs_to_hex
>   * @dst: Buffer to take hex character representation of contents of
>   *       src; must be at least of size (src_size * 2)
> - * @src: Buffer to be converted to a hex string respresentation
> + * @src: Buffer to be converted to a hex string representation
>   * @src_size: number of bytes to convert
>   */
>  void ecryptfs_to_hex(char *dst, char *src, size_t src_size)
> @@ -60,7 +60,7 @@ void ecryptfs_to_hex(char *dst, char *src, size_t src_size)
>   * ecryptfs_from_hex
>   * @dst: Buffer to take the bytes from src hex; must be at least of
>   *       size (src_size / 2)
> - * @src: Buffer to be converted from a hex string respresentation to raw value
> + * @src: Buffer to be converted from a hex string representation to raw value
>   * @dst_size: size of dst buffer, or number of hex characters pairs to convert
>   */
>  void ecryptfs_from_hex(char *dst, char *src, int dst_size)
> @@ -953,7 +953,7 @@ struct ecryptfs_cipher_code_str_map_elem {
>  };
>  
>  /* Add support for additional ciphers by adding elements here. The
> - * cipher_code is whatever OpenPGP applicatoins use to identify the
> + * cipher_code is whatever OpenPGP applications use to identify the
>   * ciphers. List in order of probability. */
>  static struct ecryptfs_cipher_code_str_map_elem
>  ecryptfs_cipher_code_str_map[] = {
> @@ -1410,7 +1410,7 @@ int ecryptfs_read_and_validate_xattr_region(struct dentry *dentry,
>   *
>   * Common entry point for reading file metadata. From here, we could
>   * retrieve the header information from the header region of the file,
> - * the xattr region of the file, or some other repostory that is
> + * the xattr region of the file, or some other repository that is
>   * stored separately from the file itself. The current implementation
>   * supports retrieving the metadata information from the file contents
>   * and from the xattr region.
> diff --git a/fs/ecryptfs/file.c b/fs/ecryptfs/file.c
> index 7000b96..53d0141 100644
> --- a/fs/ecryptfs/file.c
> +++ b/fs/ecryptfs/file.c
> @@ -171,7 +171,7 @@ out:
>  
>  /**
>   * ecryptfs_open
> - * @inode: inode speciying file to open
> + * @inode: inode specifying file to open
>   * @file: Structure to return filled in
>   *
>   * Opens the file specified by inode.
> @@ -240,7 +240,7 @@ out:
>  
>  /**
>   * ecryptfs_dir_open
> - * @inode: inode speciying file to open
> + * @inode: inode specifying file to open
>   * @file: Structure to return filled in
>   *
>   * Opens the file specified by inode.
> 




Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)