From: Yangtao Li <frank.li@vivo.com>
To: Mark Fasheh <mark@fasheh.com>, Joel Becker <jlbec@evilplan.org>,
Joseph Qi <joseph.qi@linux.alibaba.com>
Cc: Yangtao Li <frank.li@vivo.com>,
ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org
Subject: [PATCH v2 08/10] ocfs2: convert to kobject_del_and_put()
Date: Sun, 19 Mar 2023 16:41:31 +0800 [thread overview]
Message-ID: <20230319084134.11804-8-frank.li@vivo.com> (raw)
In-Reply-To: <20230319084134.11804-1-frank.li@vivo.com>
Use kobject_del_and_put() to simplify code.
Signed-off-by: Yangtao Li <frank.li@vivo.com>
---
fs/ocfs2/filecheck.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/fs/ocfs2/filecheck.c b/fs/ocfs2/filecheck.c
index 1ad7106741f8..fb9cf601245b 100644
--- a/fs/ocfs2/filecheck.c
+++ b/fs/ocfs2/filecheck.c
@@ -198,8 +198,7 @@ void ocfs2_filecheck_remove_sysfs(struct ocfs2_super *osb)
if (!osb->osb_fc_ent.fs_fcheck)
return;
- kobject_del(&osb->osb_fc_ent.fs_kobj);
- kobject_put(&osb->osb_fc_ent.fs_kobj);
+ kobject_del_and_put(&osb->osb_fc_ent.fs_kobj);
wait_for_completion(&osb->osb_fc_ent.fs_kobj_unregister);
ocfs2_filecheck_sysfs_free(&osb->osb_fc_ent);
}
--
2.35.1
next prev parent reply other threads:[~2023-03-19 8:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 8:41 [PATCH v2 01/10] kobject: introduce kobject_del_and_put() Yangtao Li
2023-03-19 8:41 ` [PATCH v2 02/10] f2fs: convert to kobject_del_and_put() Yangtao Li
2023-03-19 8:41 ` [PATCH v2 03/10] erofs: " Yangtao Li
2023-03-19 8:41 ` [PATCH v2 04/10] zonefs: " Yangtao Li
2023-03-19 8:41 ` [PATCH v2 05/10] ubifs: " Yangtao Li
2023-03-19 8:41 ` [PATCH v2 06/10] btrfs: " Yangtao Li
2023-03-19 8:41 ` [PATCH v2 07/10] xfs: " Yangtao Li
2023-03-19 8:41 ` Yangtao Li [this message]
2023-03-19 8:41 ` [PATCH v2 09/10] nfs: " Yangtao Li
2023-03-19 8:41 ` [PATCH v2 10/10] nilfs2: " Yangtao Li
2023-03-19 9:08 ` [PATCH v2 01/10] kobject: introduce kobject_del_and_put() Greg Kroah-Hartman
2023-03-19 9:36 ` Yangtao Li
2023-03-19 10:06 ` Greg KH
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=20230319084134.11804-8-frank.li@vivo.com \
--to=frank.li@vivo.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@oss.oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®