Re: [patch 3/3] fs/cramfs/inode.c: remove error variable

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Andi Drebes wrote:
Am Freitag, 31. August 2007 18:12 schrieb Nishanth Aravamudan:
On 31.08.2007 [13:43:18 +0200], Richard Knutsson wrote:
Andi Drebes wrote:
This patch removes a variable from fs/cramfs/inode.c that is just used to store
a return value which is immediately read afterwards.

Tested on an i386 box.
Signed-off-by: Andi Drebes <lists-receive@xxxxxxxxxxxxxxxxxxx>
---
diff --git a/fs/cramfs/inode.c b/fs/cramfs/inode.c
index 350680f..42d2cf8 100644
--- a/fs/cramfs/inode.c
+++ b/fs/cramfs/inode.c
@@ -372,7 +372,7 @@ static int cramfs_readdir(struct file *filp, void *dirent, filldir_t filldir)
		char *name;
		ino_t ino;
		mode_t mode;
-		int namelen, error;
+		int namelen;

		mutex_lock(&read_mutex);
de = cramfs_read(sb, OFFSET(inode) + offset, sizeof(*de)+CRAMFS_MAXPATHLEN); @@ -398,8 +398,7 @@ static int cramfs_readdir(struct file *filp, void *dirent, filldir_t filldir)
				break;
			namelen--;
		}
- error = filldir(dirent, buf, namelen, offset, ino, mode >> 12);
-		if (error)
+		if(filldir(dirent, buf, namelen, offset, ino, mode >> 12))
Maybe picky but please leave it as "if (".
Beyond that, I just don't like this change. I thought the preferred way
for these types of statements was the previous version. That is:

error = filldir(...);
if (error)
	error stuff

Rather than a conditional with potential side-effects?
OK. Maybe I exaggerated a little bit with this change. The most important
ones are those in patch 1/3 and 2/3. Maybe the best thing is to abolish the
last patch that deals with the error variable and to apply only the first two
patches.
Better/easier to do too much and cut it down a little then the other way around. ;)
I didn't really get why "if (foo)" is better than "if(foo)". Is it just a matter of style?
See the all mighty CodingStyle on 3.1
(however, it should not be taken too far but I don't see the advantage to make it "if(")

cu
Richard Knutsson

-
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Kernel Development]     [Kernel Announce]     [Kernel Newbies]     [Linux Networking Development]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Device Mapper]

  Powered by Linux