From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Yangtao Li <frank.li@vivo.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 01/10] kobject: introduce kobject_del_and_put()
Date: Sun, 19 Mar 2023 10:08:30 +0100 [thread overview]
Message-ID: <ZBbRDl4OYGZIlx7E@kroah.com> (raw)
In-Reply-To: <20230319084134.11804-1-frank.li@vivo.com>
On Sun, Mar 19, 2023 at 04:41:24PM +0800, Yangtao Li wrote:
> There are plenty of using kobject_del() and kobject_put() together
> in the kernel tree. This patch wraps these two calls in a single helper.
>
> Signed-off-by: Yangtao Li <frank.li@vivo.com>
> ---
> v2:
> -add kobject_del_and_put() users
> include/linux/kobject.h | 1 +
> lib/kobject.c | 17 +++++++++++++++--
> 2 files changed, 16 insertions(+), 2 deletions(-)
Any reason you only sent me one patch? I guess you don't want me to
review them? :(
next prev parent reply other threads:[~2023-03-19 9:10 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 ` [PATCH v2 08/10] ocfs2: " Yangtao Li
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 ` Greg Kroah-Hartman [this message]
2023-03-19 9:36 ` kobject: introduce kobject_del_and_put() 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=ZBbRDl4OYGZIlx7E@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=frank.li@vivo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox