From: Taehee Yoo <ap420073@gmail.com>
To: jaegeuk@kernel.org, cm224.lee@samsung.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: [PATCH] f2fs: remove duplicated code in the f2fs_lookup()
Date: Thu, 16 Apr 2015 17:42:43 +0900 [thread overview]
Message-ID: <1429173763-12707-1-git-send-email-ap420073@gmail.com> (raw)
in the f2fs_lookup(), checks that inode isn't null
but d_splice_alias() has same routine at first line.
so i remove this routine.
Signed-off-by: Taehee Yoo <ap420073@gmail.com>
---
fs/f2fs/namei.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/fs/f2fs/namei.c b/fs/f2fs/namei.c
index e79639a9..f17b4b5 100644
--- a/fs/f2fs/namei.c
+++ b/fs/f2fs/namei.c
@@ -204,8 +204,6 @@ static struct dentry *f2fs_lookup(struct inode *dir, struct dentry *dentry,
f2fs_put_page(page, 0);
inode = f2fs_iget(dir->i_sb, ino);
- if (IS_ERR(inode))
- return ERR_CAST(inode);
}
return d_splice_alias(inode, dentry);
--
1.9.1
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
next reply other threads:[~2015-04-16 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 8:42 Taehee Yoo [this message]
2015-04-16 17:00 ` [PATCH] f2fs: remove duplicated code in the f2fs_lookup() Jaegeuk Kim
2015-04-16 17:37 ` Taehee Yoo
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=1429173763-12707-1-git-send-email-ap420073@gmail.com \
--to=ap420073@gmail.com \
--cc=cm224.lee@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).