From: Luis Chamberlain <mcgrof@kernel.org>
To: tangmeng <tangmeng@uniontech.com>, Zhen Ni <nizhen@uniontech.com>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
peterz@infradead.org
Cc: keescook@chromium.org, yzaikin@google.com,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] kernel/reboot: move reboot sysctls to its own file
Date: Wed, 16 Feb 2022 23:53:36 -0800 [thread overview]
Message-ID: <Yg3/AByca1X4EJHo@bombadil.infradead.org> (raw)
In-Reply-To: <20220217042321.10291-1-tangmeng@uniontech.com>
On Thu, Feb 17, 2022 at 12:23:21PM +0800, tangmeng wrote:
> kernel/sysctl.c is a kitchen sink where everyone leaves their dirty
> dishes, this makes it very difficult to maintain.
>
> To help with this maintenance let's start by moving sysctls to places
> where they actually belong. The proc sysctl maintainers do not want to
> know what sysctl knobs you wish to add for your own piece of code, we
> just care about the core logic.
>
> All filesystem syctls now get reviewed by fs folks. This commit
> follows the commit of fs, move the poweroff_cmd and ctrl-alt-del
> sysctls to its own file, kernel/reboot.c.
>
> Signed-off-by: tangmeng <tangmeng@uniontech.com>
Queued onto sysctl-next [0]. This tree is intended to queue up all of
the sysctl changes, get them tested.
[0] https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git/log/?h=sysctl-next
Luis
prev parent reply other threads:[~2022-02-17 7:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 4:23 [PATCH] kernel/reboot: move reboot sysctls to its own file tangmeng
2022-02-17 7:53 ` Luis Chamberlain [this message]
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=Yg3/AByca1X4EJHo@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nizhen@uniontech.com \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tangmeng@uniontech.com \
--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).