linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: yingelin <yingelin@huawei.com>
Cc: ebiederm@xmission.com, keescook@chromium.org, yzaikin@google.com,
	kexec@lists.infradead.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, chenjianguo3@huawei.com,
	nixiaoming@huawei.com, qiuguorui1@huawei.com,
	young.liuyang@huawei.com, zengweilin@huawei.com
Subject: Re: [PATCH sysctl-testing v2] kernel/kexec_core: move kexec_core sysctls into its own file
Date: Mon, 25 Apr 2022 14:02:02 -0700	[thread overview]
Message-ID: <YmcMSkI8ea/Ncz4y@bombadil.infradead.org> (raw)
In-Reply-To: <20220424025740.50371-1-yingelin@huawei.com>

On Sun, Apr 24, 2022 at 10:57:40AM +0800, yingelin wrote:
> This move the kernel/kexec_core.c respective sysctls to its own file.
> 
> kernel/sysctl.c has grown to an insane mess, We move sysctls to places
> where features actually belong to improve the readability and reduce
> merge conflicts. At the same time, the proc-sysctl maintainers can easily
> care about the core logic other than the sysctl knobs added for some feature.
> 
> We already moved all filesystem sysctls out. This patch is part of the effort
> to move kexec related sysctls out.
> 
> Signed-off-by: yingelin <yingelin@huawei.com>

Thanks! Queued onto sysctl-testing.

  Luis

      parent reply	other threads:[~2022-04-25 21:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-24  2:57 [PATCH sysctl-testing v2] kernel/kexec_core: move kexec_core sysctls into its own file yingelin
2022-04-25  1:28 ` Baoquan He
2022-04-25 21:02 ` 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=YmcMSkI8ea/Ncz4y@bombadil.infradead.org \
    --to=mcgrof@kernel.org \
    --cc=chenjianguo3@huawei.com \
    --cc=ebiederm@xmission.com \
    --cc=keescook@chromium.org \
    --cc=kexec@lists.infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nixiaoming@huawei.com \
    --cc=qiuguorui1@huawei.com \
    --cc=yingelin@huawei.com \
    --cc=young.liuyang@huawei.com \
    --cc=yzaikin@google.com \
    --cc=zengweilin@huawei.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).