From: Xiaoming Ni <nixiaoming@huawei.com>
To: <mcgrof@kernel.org>, <keescook@chromium.org>,
<yzaikin@google.com>, <adobriyan@gmail.com>, <mingo@kernel.org>,
<peterz@infradead.org>, <akpm@linux-foundation.org>,
<yamada.masahiro@socionext.com>, <bauerman@linux.ibm.com>,
<gregkh@linuxfoundation.org>, <skhan@linuxfoundation.org>,
<dvyukov@google.com>, <svens@stackframe.org>,
<joel@joelfernandes.org>, <tglx@linutronix.de>,
<Jisheng.Zhang@synaptics.com>, <pmladek@suse.com>,
<bigeasy@linutronix.de>
Cc: <linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<nixiaoming@huawei.com>, <wangle6@huawei.com>
Subject: [PATCH 0/4] Move the sysctl interface to the corresponding feature code file
Date: Fri, 15 May 2020 12:33:40 +0800 [thread overview]
Message-ID: <1589517224-123928-1-git-send-email-nixiaoming@huawei.com> (raw)
Use register_sysctl() to register the sysctl interface to avoid
merge conflicts when different features modify sysctl.c at the same time.
Here, the sysctl interfaces of hung task and watchdog are moved to the
corresponding feature code files
https://lkml.org/lkml/2020/5/11/1419
Xiaoming Ni (4):
hung_task: Move hung_task syscl interface to hung_task_sysctl.c
proc/sysctl: add shared variables -1
watchdog: move watchdog sysctl to watchdog.c
sysctl: Add register_sysctl_init() interface
fs/proc/proc_sysctl.c | 2 +-
include/linux/sched/sysctl.h | 8 +--
include/linux/sysctl.h | 3 +
kernel/Makefile | 4 +-
kernel/hung_task.c | 6 +-
kernel/hung_task.h | 21 ++++++
kernel/hung_task_sysctl.c | 66 +++++++++++++++++
kernel/sysctl.c | 168 ++++++-------------------------------------
kernel/watchdog.c | 101 ++++++++++++++++++++++++++
9 files changed, 219 insertions(+), 160 deletions(-)
create mode 100644 kernel/hung_task.h
create mode 100644 kernel/hung_task_sysctl.c
--
1.8.5.6
next reply other threads:[~2020-05-15 4:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 4:33 Xiaoming Ni [this message]
2020-05-15 4:33 ` [PATCH 1/4] hung_task: Move hung_task sysctl interface to hung_task_sysctl.c Xiaoming Ni
2020-05-15 8:04 ` Kees Cook
2020-05-15 8:56 ` Xiaoming Ni
2020-05-15 16:03 ` Kees Cook
2020-05-15 20:21 ` Luis Chamberlain
2020-05-15 4:33 ` [PATCH 2/4] proc/sysctl: add shared variables -1 Xiaoming Ni
2020-05-15 8:06 ` Kees Cook
2020-05-15 9:06 ` Xiaoming Ni
2020-05-15 16:05 ` Kees Cook
2020-05-16 2:32 ` Xiaoming Ni
2020-05-16 2:47 ` Kees Cook
2020-05-16 3:05 ` Xiaoming Ni
2020-05-17 2:38 ` Kees Cook
2020-05-15 4:33 ` [PATCH 3/4] watchdog: move watchdog sysctl to watchdog.c Xiaoming Ni
2020-05-15 8:09 ` Kees Cook
2020-05-15 9:17 ` Xiaoming Ni
2020-05-15 4:33 ` [PATCH 4/4] sysctl: Add register_sysctl_init() interface Xiaoming Ni
2020-05-15 8:10 ` Kees Cook
2020-05-15 9:39 ` Xiaoming Ni
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=1589517224-123928-1-git-send-email-nixiaoming@huawei.com \
--to=nixiaoming@huawei.com \
--cc=Jisheng.Zhang@synaptics.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bauerman@linux.ibm.com \
--cc=bigeasy@linutronix.de \
--cc=dvyukov@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=joel@joelfernandes.org \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=skhan@linuxfoundation.org \
--cc=svens@stackframe.org \
--cc=tglx@linutronix.de \
--cc=wangle6@huawei.com \
--cc=yamada.masahiro@socionext.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 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.