From: Luis Chamberlain <mcgrof@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ebiederm@xmission.com, keescook@chromium.org, yzaikin@google.com,
j.granados@samsung.com, patches@lists.linux.dev,
ebiggers@kernel.org, jeffxu@google.com,
akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, mcgrof@kernel.org
Subject: [GIT PULL] sysctl changes for v6.4-rc4 v2
Date: Wed, 3 May 2023 12:17:57 -0700 [thread overview]
Message-ID: <ZFKzZeAs5Mdfv5ha@bombadil.infradead.org> (raw)
The following changes since commit 348551ddaf311c76b01cdcbaf61b6fef06a49144:
Merge tag 'pinctrl-v6.4-1' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl (2023-05-02 15:40:41 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git/ tags/sysctl-6.4-rc1-v2
for you to fetch changes up to 0199849acd07d07e2a8e42757653ca8b14a122f5:
sysctl: remove register_sysctl_paths() (2023-05-02 19:24:16 -0700)
----------------------------------------------------------------
sysctl-6.4-rc1-v2
As mentioned on my first pull request for sysctl-next, for v6.4-rc1
we're very close to being able to deprecating register_sysctl_paths().
I was going to assess the situation after the first week of the merge
window.
That time is now and things are looking good. We only have one stragglers
on the patch which had already an ACK for so I'm picking this up here now and
the last patch is the one that uses an axe. Some careful eyeballing would
be appreciated by others. If this doesn't get properly reviewed I can also
just hold off on this in my tree for the next merge window. Either way is
fine by me.
I have boot tested the last patch and 0-day build completed successfully.
----------------------------------------------------------------
Luis Chamberlain (2):
kernel: pid_namespace: simplify sysctls with register_sysctl()
sysctl: remove register_sysctl_paths()
fs/proc/proc_sysctl.c | 55 ++++-------------------------------------------
include/linux/sysctl.h | 12 -----------
kernel/pid_namespace.c | 3 +--
kernel/pid_sysctl.h | 3 +--
scripts/check-sysctl-docs | 16 --------------
5 files changed, 6 insertions(+), 83 deletions(-)
next reply other threads:[~2023-05-03 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 19:17 Luis Chamberlain [this message]
2023-05-04 3:13 ` [GIT PULL] sysctl changes for v6.4-rc4 v2 pr-tracker-bot
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=ZFKzZeAs5Mdfv5ha@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=ebiggers@kernel.org \
--cc=j.granados@samsung.com \
--cc=jeffxu@google.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=torvalds@linux-foundation.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).