linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yaowei Bai <bywxiaobai@163.com>
To: Boaz Harrosh <ooo@electrozaur.com>
Cc: viro@zeniv.linux.org.uk, bhalevy@primarydata.com,
	osd-dev@open-osd.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 05/17] fs/exofs: remove unnecessary new_valid_dev check
Date: Tue, 29 Sep 2015 23:46:32 +0800	[thread overview]
Message-ID: <20150929154631.GA6489@bbox> (raw)
In-Reply-To: <560A9672.9@electrozaur.com>

On Tue, Sep 29, 2015 at 04:47:30PM +0300, Boaz Harrosh wrote:
> On 09/28/2015 04:43 PM, Yaowei Bai wrote:
> > 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>
> 
> ACK-by: Boaz Harrosh <ooo@electrozaur.com>

Thanks.

> 
> Please submit this through some General tree like the vfs or mm-tree

This's my first fs-specific patch, so i think you mean i should cc vfs
or mm-tree?

> 
> Thanks
> Boaz
> 
> > ---
> >  fs/exofs/namei.c | 3 ---
> >  1 file changed, 3 deletions(-)
> > 
> > diff --git a/fs/exofs/namei.c b/fs/exofs/namei.c
> > index 09a6bb1..994e078 100644
> > --- a/fs/exofs/namei.c
> > +++ b/fs/exofs/namei.c
> > @@ -80,9 +80,6 @@ static int exofs_mknod(struct inode *dir, struct dentry *dentry, umode_t mode,
> >  	struct inode *inode;
> >  	int err;
> >  
> > -	if (!new_valid_dev(rdev))
> > -		return -EINVAL;
> > -
> >  	inode = exofs_new_inode(dir, mode);
> >  	err = PTR_ERR(inode);
> >  	if (!IS_ERR(inode)) {
> > 

  reply	other threads:[~2015-09-29 15:46 UTC|newest]

Thread overview: 38+ 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 ` [PATCH 04/17] fs/btrfs: " Yaowei Bai
2015-09-29 14:55   ` 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 [this message]
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 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
     [not found] ` <1443446807-4838-1-git-send-email-bywxiaobai-9Onoh4P/yGk@public.gmane.org>
2015-09-28 14:30   ` [PATCH 13/17] fs/nfs: " Yaowei Bai
2015-09-28 14:33 ` [PATCH 14/17] fs/nilfs2: " Yaowei Bai
     [not found]   ` <1443450823-5692-1-git-send-email-bywxiaobai-9Onoh4P/yGk@public.gmane.org>
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

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=20150929154631.GA6489@bbox \
    --to=bywxiaobai@163.com \
    --cc=bhalevy@primarydata.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ooo@electrozaur.com \
    --cc=osd-dev@open-osd.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 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).