From: Greg KH <gregkh@linuxfoundation.org>
To: Alexander Aring <aahringo@redhat.com>
Cc: teigland@redhat.com, gfs2@lists.linux.dev, song@kernel.org,
yukuai3@huawei.com, agruenba@redhat.com, mark@fasheh.com,
jlbec@evilplan.org, joseph.qi@linux.alibaba.com,
rafael@kernel.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
ocfs2-devel@lists.linux.dev, lucien.xin@gmail.com
Subject: Re: [RFC dlm/next 08/12] kobject: add kset_type_create_and_add() helper
Date: Sat, 24 Aug 2024 10:26:09 +0800 [thread overview]
Message-ID: <2024082459-neatly-screen-9d29@gregkh> (raw)
In-Reply-To: <20240814143414.1877505-9-aahringo@redhat.com>
On Wed, Aug 14, 2024 at 10:34:10AM -0400, Alexander Aring wrote:
> Currently there exists the kset_create_and_add() helper that does not
> allow to have a different ktype for the created kset kobject. To allow
> a different ktype this patch will introduce the function
> kset_type_create_and_add() that allows to set a different ktype instead
> of using the global default kset_ktype variable.
>
> In my example I need to separate the created kobject inside the kset by
> net-namespaces. This patch allows me to do that by providing a user
> defined kobj_type structure that implements the necessary namespace
> functionality.
>
> Signed-off-by: Alexander Aring <aahringo@redhat.com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2024-08-24 5:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 14:34 [RFC dlm/next 00/12] dlm: net-namespace functionality Alexander Aring
2024-08-14 14:34 ` [RFC dlm/next 01/12] dlm: introduce dlm_find_lockspace_name() Alexander Aring
2024-08-14 14:34 ` [RFC dlm/next 02/12] dlm: disallow different configs nodeid storages Alexander Aring
2024-08-14 14:34 ` [RFC dlm/next 03/12] dlm: add struct net to dlm_new_lockspace() Alexander Aring
2024-08-14 14:34 ` [RFC dlm/next 04/12] dlm: handle port as __be16 network byte order Alexander Aring
2024-08-14 14:34 ` [RFC dlm/next 05/12] dlm: use dlm_config as only cluster configuration Alexander Aring
2024-08-14 14:34 ` [RFC dlm/next 06/12] dlm: dlm_config_info config fields to unsigned int Alexander Aring
2024-08-14 14:34 ` [RFC dlm/next 07/12] dlm: rename config to configfs Alexander Aring
2024-08-14 14:34 ` [RFC dlm/next 08/12] kobject: add kset_type_create_and_add() helper Alexander Aring
2024-08-24 2:26 ` Greg KH [this message]
2024-08-25 19:54 ` Alexander Aring
2024-08-14 14:34 ` [RFC dlm/next 09/12] kobject: export generic helper ops Alexander Aring
2024-08-14 15:05 ` Greg KH
2024-08-14 20:47 ` Alexander Aring
2024-08-15 5:28 ` Greg KH
2024-08-14 14:34 ` [RFC dlm/next 10/12] dlm: separate dlm lockspaces per net-namespace Alexander Aring
2024-08-14 14:34 ` [RFC dlm/next 11/12] dlm: add nldlm net-namespace aware UAPI Alexander Aring
2024-08-14 14:34 ` [RFC dlm/next 12/12] gfs2: separate mount context by net-namespaces Alexander Aring
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=2024082459-neatly-screen-9d29@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=aahringo@redhat.com \
--cc=agruenba@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=gfs2@lists.linux.dev \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=song@kernel.org \
--cc=teigland@redhat.com \
--cc=yukuai3@huawei.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;
as well as URLs for NNTP newsgroup(s).