renegade-project/linux-next
2
0
Fork 0
mirror of https://github.com/edk2-porting/linux-next.git synced 2024-12-15 08:44:14 +08:00
Code

ecryptfs: fix spelling mistakes

Browse Source 
Noticed some minor spelling errors when looking through the code.

Signed-off-by: Chris J Arges <chris.j.arges@canonical.com>
Signed-off-by: Tyler Hicks <tyhicks@canonical.com>
This commit is contained in:
Chris J Arges 2016-06-09 15:31:29 -05:00 committed by Tyler Hicks
parent 5f9f2c2abd
commit 40f0fd372a
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
fs/ecryptfs/crypto.c
View File

@ -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.

4
fs/ecryptfs/file.c
View File

@ -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.