All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yaowei Bai <bywxiaobai@163.com>
To: viro@zeniv.linux.org.uk, clm@fb.com, jbacik@fb.com, dsterba@suse.com
Cc: linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 04/17] fs/btrfs: remove unnecessary new_valid_dev check
Date: Mon, 28 Sep 2015 21:39:00 +0800	[thread overview]
Message-ID: <1443447540-5098-1-git-send-email-bywxiaobai@163.com> (raw)
In-Reply-To: <1443446807-4838-1-git-send-email-bywxiaobai@163.com>

As new_valid_dev always returns 1, so !new_valid_dev check is not
needed, remove it.

Signed-off-by: Yaowei Bai <bywxiaobai@163.com>
---
 fs/btrfs/inode.c | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
index 611b66d..0946790 100644
--- a/fs/btrfs/inode.c
+++ b/fs/btrfs/inode.c
@@ -6268,9 +6268,6 @@ static int btrfs_mknod(struct inode *dir, struct dentry *dentry,
 	u64 objectid;
 	u64 index = 0;
 
-	if (!new_valid_dev(rdev))
-		return -EINVAL;
-
 	/*
 	 * 2 for inode item and ref
 	 * 2 for dir items
-- 
1.9.1



  parent reply	other threads:[~2015-09-28 13:41 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-28 13:26 [PATCH 00/17] cleanups of fs about new/huge_valid_dev Yaowei Bai
2015-09-28 13:29 ` [PATCH 01/17] fs/kdev_t: remove unused huge_valid_dev function Yaowei Bai
2015-09-28 13:29   ` [PATCH 02/17] fs/kdev_t: old/new_valid_dev can be boolean Yaowei Bai
2015-09-28 13:34 ` [PATCH 03/17] fs/vfs: remove unnecessary new_valid_dev check Yaowei Bai
2015-09-28 13:39 ` Yaowei Bai [this message]
2015-09-29 14:55   ` [PATCH 04/17] fs/btrfs: " David Sterba
2015-09-28 13:43 ` [PATCH 05/17] fs/exofs: " Yaowei Bai
2015-09-29 13:47   ` Boaz Harrosh
2015-09-29 15:46     ` Yaowei Bai
2015-09-30 10:26       ` Boaz Harrosh
2015-10-08 12:29     ` Yaowei Bai
2015-09-28 13:47 ` [PATCH 06/17] fs/ext2: " Yaowei Bai
2015-09-28 13:50 ` [PATCH 07/17] fs/ext4: " Yaowei Bai
2015-10-29 18:09   ` Theodore Ts'o
2015-10-30  1:38     ` Yaowei Bai
2015-09-28 13:55 ` [PATCH 08/17] fs/f2fs: " Yaowei Bai
2015-09-28 13:55   ` Yaowei Bai
2015-09-28 14:11 ` [PATCH 09/17] fs/hpfs: " Yaowei Bai
2015-09-29 15:03   ` Mikulas Patocka
2015-09-30 11:13     ` Yaowei Bai
2015-10-01 20:49       ` Mikulas Patocka
2015-10-08 12:22         ` Yaowei Bai
2015-09-28 14:15 ` [PATCH 10/17] fs/jffs2: " Yaowei Bai
2015-09-28 23:20   ` Brian Norris
2015-09-28 14:18 ` [PATCH 11/17] fs/jfs: " Yaowei Bai
2015-09-28 15:42   ` [Jfs-discussion] " Dave Kleikamp
2015-09-28 14:21 ` [PATCH 06/17] fs/ext2: " Yaowei Bai
2015-09-28 14:25 ` [PATCH 12/17] fs/ncpfs: " Yaowei Bai
2015-09-28 14:30 ` [PATCH 13/17] fs/nfs: " Yaowei Bai
2015-09-28 14:30   ` Yaowei Bai
2015-09-28 14:33 ` [PATCH 14/17] fs/nilfs2: " Yaowei Bai
2015-09-29 14:51   ` Ryusuke Konishi
2015-09-29 14:51     ` Ryusuke Konishi
2015-09-28 14:47 ` [PATCH 15/17] fs/reiserfs: " Yaowei Bai
2015-09-28 14:50 ` [PATCH 16/17] fs/stat: " Yaowei Bai
2015-09-28 14:53 ` [PATCH 17/17] fs/ubifs: " Yaowei Bai
2015-09-28 19:20   ` Richard Weinberger
2015-09-29 13:43     ` Yaowei Bai
2015-09-29 13:57 ` [PATCH] " Yaowei Bai
2015-09-30  8:11   ` Richard Weinberger
2015-10-01 13:35     ` Artem Bityutskiy
2015-10-01 13:35       ` Artem Bityutskiy

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=1443447540-5098-1-git-send-email-bywxiaobai@163.com \
    --to=bywxiaobai@163.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=jbacik@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.