From: Adil Mujeeb <mujeeb.adil@gmail.com>
To: tytso@mit.edu, adilger.kernel@dilger.ca,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Adil Mujeeb <mujeeb.adil@gmail.com>
Subject: [PATCH 05/10] ext4: file: Fixed coding style issue
Date: Wed, 17 Oct 2012 00:43:00 +0530 [thread overview]
Message-ID: <1350414785-7848-5-git-send-email-mujeeb.adil@gmail.com> (raw)
In-Reply-To: <1350414785-7848-1-git-send-email-mujeeb.adil@gmail.com>
Removed errors reported by checkpatch.pl
Signed-off-by: Adil Mujeeb <mujeeb.adil@gmail.com>
---
linux-3.7-rc1/fs/ext4/file.c | 5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/linux-3.7-rc1/fs/ext4/file.c b/linux-3.7-rc1/fs/ext4/file.c
index bf3966b..17068a7 100644
--- a/linux-3.7-rc1/fs/ext4/file.c
+++ b/linux-3.7-rc1/fs/ext4/file.c
@@ -43,8 +43,7 @@ static int ext4_release_file(struct inode *inode, struct file *filp)
/* if we are the last writer on the inode, drop the block reservation */
if ((filp->f_mode & FMODE_WRITE) &&
(atomic_read(&inode->i_writecount) == 1) &&
- !EXT4_I(inode)->i_reserved_data_blocks)
- {
+ !EXT4_I(inode)->i_reserved_data_blocks) {
down_write(&EXT4_I(inode)->i_data_sem);
ext4_discard_preallocations(inode);
up_write(&EXT4_I(inode)->i_data_sem);
@@ -221,7 +220,7 @@ static int ext4_file_mmap(struct file *file, struct vm_area_struct *vma)
return 0;
}
-static int ext4_file_open(struct inode * inode, struct file * filp)
+static int ext4_file_open(struct inode *inode, struct file *filp)
{
struct super_block *sb = inode->i_sb;
struct ext4_sb_info *sbi = EXT4_SB(inode->i_sb);
--
1.7.7.3
next prev parent reply other threads:[~2012-10-16 19:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 19:12 [PATCH 01/10] ext4: balloc: Fixed coding style issue Adil Mujeeb
2012-10-16 19:12 ` [PATCH 02/10] ext4: block_validity: " Adil Mujeeb
2012-10-16 19:12 ` [PATCH 03/10] ext4: ext4.h: fixed " Adil Mujeeb
2012-10-16 19:12 ` [PATCH 04/10] ext4: extents: Fixed " Adil Mujeeb
2012-10-16 19:13 ` Adil Mujeeb [this message]
2012-10-16 19:13 ` [PATCH 06/10] ext4: ialloc: " Adil Mujeeb
2012-10-16 19:13 ` [PATCH 07/10] ext4: inode: " Adil Mujeeb
2012-10-16 19:13 ` [PATCH 08/10] ext4: ioctl: " Adil Mujeeb
2012-10-16 19:13 ` [PATCH 09/10] ext4: namei: " Adil Mujeeb
2012-10-16 19:13 ` [PATCH 10/10] ext4: resize: " Adil Mujeeb
2012-10-17 12:05 ` [PATCH 01/10] ext4: balloc: " Lukáš Czerner
2012-10-17 12:13 ` richard -rw- weinberger
[not found] ` <CANBXnMkoFo1HdQZkOq0HR4aLX_LObXB2=mEpiHBwK2CSK_hCKA@mail.gmail.com>
2012-10-17 14:27 ` Lukáš Czerner
2012-10-17 16:52 ` Adil Mujeeb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1350414785-7848-5-git-send-email-mujeeb.adil@gmail.com \
--to=mujeeb.adil@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).