All of lore.kernel.org
 help / color / mirror / Atom feed
From: yuzhe <yuzhe@nfschina.com>
To: trond.myklebust@hammerspace.com, anna@kernel.org
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org, liqiong@nfschina.com,
	yuzhe <yuzhe@nfschina.com>
Subject: [PATCH] NFSv4: remove unnecessary (void*) conversions.
Date: Wed, 23 Mar 2022 03:06:09 -0700	[thread overview]
Message-ID: <20220323100609.183087-1-yuzhe@nfschina.com> (raw)

No need cast (void*) to (struct idmap *).

Signed-off-by: yuzhe <yuzhe@nfschina.com>
---
 fs/nfs/nfs4idmap.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/fs/nfs/nfs4idmap.c b/fs/nfs/nfs4idmap.c
index f331866dd418..6d4d602235be 100644
--- a/fs/nfs/nfs4idmap.c
+++ b/fs/nfs/nfs4idmap.c
@@ -668,7 +668,7 @@ idmap_pipe_downcall(struct file *filp, const char __user *src, size_t mlen)
 {
 	struct request_key_auth *rka;
 	struct rpc_inode *rpci = RPC_I(file_inode(filp));
-	struct idmap *idmap = (struct idmap *)rpci->private;
+	struct idmap *idmap = rpci->private;
 	struct key *authkey;
 	struct idmap_msg im;
 	size_t namelen_in;
@@ -735,7 +735,7 @@ static void
 idmap_release_pipe(struct inode *inode)
 {
 	struct rpc_inode *rpci = RPC_I(inode);
-	struct idmap *idmap = (struct idmap *)rpci->private;
+	struct idmap *idmap = rpci->private;
 
 	nfs_idmap_abort_pipe_upcall(idmap, -EPIPE);
 }
-- 
2.25.1


             reply	other threads:[~2022-03-23 10:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-23 10:06 yuzhe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-03-23 10:05 [PATCH] NFSv4: remove unnecessary (void*) conversions yuzhe

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=20220323100609.183087-1-yuzhe@nfschina.com \
    --to=yuzhe@nfschina.com \
    --cc=anna@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=liqiong@nfschina.com \
    --cc=trond.myklebust@hammerspace.com \
    /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.