From: Jakub Kicinski <kuba@kernel.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Roopa Prabhu <roopa@nvidia.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna@kernel.org>,
Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>,
bridge@lists.linux-foundation.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/3] net: make kobj_type structures constant
Date: Mon, 13 Feb 2023 20:11:31 -0800 [thread overview]
Message-ID: <20230213201131.7ed238f9@kernel.org> (raw)
In-Reply-To: <20230211-kobj_type-net-v1-0-e3bdaa5d8a78@weissschuh.net>
On Sat, 11 Feb 2023 03:32:28 +0000 Thomas Weißschuh wrote:
> Since commit ee6d3dd4ed48 ("driver core: make kobj_type constant.")
> the driver core allows the usage of const struct kobj_type.
>
> Take advantage of this to constify the structure definitions to prevent
> modification at runtime.
Could you resend just the first two with [PATCH net-next] in the
subject? Patch 3 needs to go to a different tree.
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: linux-nfs@vger.kernel.org, netdev@vger.kernel.org,
Nikolay Aleksandrov <razor@blackwall.org>,
bridge@lists.linux-foundation.org,
Jeff Layton <jlayton@kernel.org>,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Chuck Lever <chuck.lever@oracle.com>,
Anna Schumaker <anna@kernel.org>, Roopa Prabhu <roopa@nvidia.com>,
Paolo Abeni <pabeni@redhat.com>,
Trond Myklebust <trond.myklebust@hammerspace.com>
Subject: Re: [Bridge] [PATCH 0/3] net: make kobj_type structures constant
Date: Mon, 13 Feb 2023 20:11:31 -0800 [thread overview]
Message-ID: <20230213201131.7ed238f9@kernel.org> (raw)
In-Reply-To: <20230211-kobj_type-net-v1-0-e3bdaa5d8a78@weissschuh.net>
On Sat, 11 Feb 2023 03:32:28 +0000 Thomas Weißschuh wrote:
> Since commit ee6d3dd4ed48 ("driver core: make kobj_type constant.")
> the driver core allows the usage of const struct kobj_type.
>
> Take advantage of this to constify the structure definitions to prevent
> modification at runtime.
Could you resend just the first two with [PATCH net-next] in the
subject? Patch 3 needs to go to a different tree.
next prev parent reply other threads:[~2023-02-14 4:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 3:32 [PATCH 0/3] net: make kobj_type structures constant Thomas Weißschuh
2023-02-11 3:32 ` [Bridge] " Thomas Weißschuh
2023-02-11 3:32 ` [PATCH 1/3] net: bridge: make kobj_type structure constant Thomas Weißschuh
2023-02-11 3:32 ` [Bridge] " Thomas Weißschuh
2023-02-11 3:32 ` [PATCH 2/3] net-sysfs: make kobj_type structures constant Thomas Weißschuh
2023-02-11 3:32 ` [Bridge] " Thomas Weißschuh
2023-02-11 3:32 ` [PATCH 3/3] SUNRPC: " Thomas Weißschuh
2023-02-11 3:32 ` [Bridge] " Thomas Weißschuh
2023-02-14 4:11 ` Jakub Kicinski [this message]
2023-02-14 4:11 ` [Bridge] [PATCH 0/3] net: " Jakub Kicinski
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=20230213201131.7ed238f9@kernel.org \
--to=kuba@kernel.org \
--cc=anna@kernel.org \
--cc=bridge@lists.linux-foundation.org \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.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.