All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikulas Patocka <mikulas@twibright.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH] hpfs: Remove unessary cast
Date: Sun, 28 Jun 2015 15:18:51 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.00.1506281518020.29365@leontynka> (raw)

From: Firo Yang <firogm@gmail.com>
Date: Thu, 23 Apr 2015 17:28:45 +0800

Avoid a pointless kmem_cache_alloc() return value cast in
fs/hpfs/super.c::hpfs_alloc_inode()

Signed-off-by: Firo Yang <firogm@gmail.com>
Signed-off-by: Mikulas Patocka <mikulas@twibright.com>
---
 fs/hpfs/super.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: linux-4.1/fs/hpfs/super.c
===================================================================
--- linux-4.1.orig/fs/hpfs/super.c	2015-06-22 20:17:54.000000000 +0200
+++ linux-4.1/fs/hpfs/super.c	2015-06-22 21:27:59.000000000 +0200
@@ -238,7 +238,7 @@ static struct kmem_cache * hpfs_inode_ca
 static struct inode *hpfs_alloc_inode(struct super_block *sb)
 {
 	struct hpfs_inode_info *ei;
-	ei = (struct hpfs_inode_info *)kmem_cache_alloc(hpfs_inode_cachep, GFP_NOFS);
+	ei = kmem_cache_alloc(hpfs_inode_cachep, GFP_NOFS);
 	if (!ei)
 		return NULL;
 	ei->vfs_inode.i_version = 1;

             reply	other threads:[~2015-06-28 13:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-28 13:18 Mikulas Patocka [this message]
2015-06-29  8:19 ` [PATCH] hpfs: Remove unessary cast Sohny Thomas
  -- strict thread matches above, loose matches on Subject: below --
2015-05-02 17:12 Mikulas Patocka
2015-04-23  9:28 Firo Yang
2015-05-02  8:10 ` Mikulas Patocka
2015-05-02 16:30   ` Linus Torvalds
2015-05-02 17:13     ` Mikulas Patocka

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=alpine.DEB.2.00.1506281518020.29365@leontynka \
    --to=mikulas@twibright.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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.