From: Joel Granados <j.granados@samsung.com>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
Kees Cook <keescook@chromium.org>,
Iurii Zaikin <yzaikin@google.com>, <linux-kernel@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] sysctl: remove struct ctl_path
Date: Sat, 23 Dec 2023 14:12:24 +0100 [thread overview]
Message-ID: <20231223131224.phe54a3smekirek3@localhost> (raw)
In-Reply-To: <20231220-sysctl-paths-v1-1-e123e3e704db@weissschuh.net>
[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]
On Wed, Dec 20, 2023 at 10:23:35PM +0100, Thomas Weißschuh wrote:
> All usages of this struct have been removed from the kernel tree.
>
> The struct is still referenced by scripts/check-sysctl-docs but that
> script is broken anyways as it only supports the register_sysctl_paths()
> API and not the currently used register_sysctl() one.
>
> Fixes: 0199849acd07 ("sysctl: remove register_sysctl_paths()")
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> ---
> include/linux/sysctl.h | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/include/linux/sysctl.h b/include/linux/sysctl.h
> index 61b40ea81f4d..8084e9132833 100644
> --- a/include/linux/sysctl.h
> +++ b/include/linux/sysctl.h
> @@ -210,11 +210,6 @@ struct ctl_table_root {
> int (*permissions)(struct ctl_table_header *head, struct ctl_table *table);
> };
>
> -/* struct ctl_path describes where in the hierarchy a table is added */
> -struct ctl_path {
> - const char *procname;
> -};
> -
> #define register_sysctl(path, table) \
> register_sysctl_sz(path, table, ARRAY_SIZE(table))
>
>
> ---
> base-commit: 1a44b0073b9235521280e19d963b6dfef7888f18
> change-id: 20231220-sysctl-paths-474697856a3f
>
> Best regards,
> --
> Thomas Weißschuh <linux@weissschuh.net>
>
LGTM
Reviewed-by: Joel Granados <j.granados@samsung.com>
--
Joel Granados
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-12-24 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20231220212343eucas1p2f905cf62bec100412a4ecdabe8916619@eucas1p2.samsung.com>
2023-12-20 21:23 ` [PATCH] sysctl: remove struct ctl_path Thomas Weißschuh
2023-12-23 13:12 ` Joel Granados [this message]
2023-12-28 13:03 ` Luis Chamberlain
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=20231223131224.phe54a3smekirek3@localhost \
--to=j.granados@samsung.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=mcgrof@kernel.org \
--cc=yzaikin@google.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).