All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Meyer <thomas@m3y3r.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] GFS2: Cocci spatch "ptr_ret.spatch"
Date: Sat, 01 Jun 2013 11:52:43 +0200	[thread overview]
Message-ID: <1370080363.29224.24.camel@localhost.localdomain> (raw)


Signed-off-by: Thomas Meyer <thomas@m3y3r.de>
---

diff -u -p a/fs/gfs2/inode.c b/fs/gfs2/inode.c
--- a/fs/gfs2/inode.c
+++ b/fs/gfs2/inode.c
@@ -587,7 +587,7 @@ static int gfs2_create_inode(struct inod
 		inode = gfs2_lookupi(dir, &dentry->d_name, 0);
 		gfs2_glock_dq_uninit(ghs);
 		d_instantiate(dentry, inode);
-		return IS_ERR(inode) ? PTR_ERR(inode) : 0;
+		return PTR_RET(inode);
 	}
 	if (error)
 		goto fail_gunlock;




WARNING: multiple messages have this Message-ID (diff)
From: Thomas Meyer <thomas@m3y3r.de>
To: cluster-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: [PATCH] GFS2: Cocci spatch "ptr_ret.spatch"
Date: Sat, 01 Jun 2013 11:52:43 +0200	[thread overview]
Message-ID: <1370080363.29224.24.camel@localhost.localdomain> (raw)


Signed-off-by: Thomas Meyer <thomas@m3y3r.de>
---

diff -u -p a/fs/gfs2/inode.c b/fs/gfs2/inode.c
--- a/fs/gfs2/inode.c
+++ b/fs/gfs2/inode.c
@@ -587,7 +587,7 @@ static int gfs2_create_inode(struct inod
 		inode = gfs2_lookupi(dir, &dentry->d_name, 0);
 		gfs2_glock_dq_uninit(ghs);
 		d_instantiate(dentry, inode);
-		return IS_ERR(inode) ? PTR_ERR(inode) : 0;
+		return PTR_RET(inode);
 	}
 	if (error)
 		goto fail_gunlock;



             reply	other threads:[~2013-06-01  9:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-01  9:52 Thomas Meyer [this message]
2013-06-01  9:52 ` [PATCH] GFS2: Cocci spatch "ptr_ret.spatch" Thomas Meyer
2013-06-03  8:55 ` [Cluster-devel] " Steven Whitehouse
2013-06-03  8:55   ` Steven Whitehouse

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=1370080363.29224.24.camel@localhost.localdomain \
    --to=thomas@m3y3r.de \
    /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.