From: yukaixiong <yukaixiong@huawei.com>
To: <"wangkefeng.wang@huawei.com liushixin2@huawei.com
liuyongqiang13@huawei.com tongtiangen@huawei.com
sunnanyong@huawei.com mawupeng1@huawei.com zuoze1@huawei.com
zhangpeng362@huawei.com tujinjiang@huawei.com
yaolulu5"@huawei.com>
Cc: <guohanjun@huawei.com>, <ysato@users.osdn.me>, <dalias@libc.org>,
<glaubitz@physik.fu-berlin.de>, <luto@kernel.org>,
<tglx@linutronix.de>, <bp@alien8.de>,
<dave.hansen@linux.intel.com>, <hpa@zytor.com>,
<viro@zeniv.linux.org.uk>, <brauner@kernel.org>, <jack@suse.cz>,
<kees@kernel.org>, <willy@infradead.org>,
<Liam.Howlett@oracle.com>, <vbabka@suse.cz>,
<lorenzo.stoakes@oracle.com>, <trondmy@kernel.org>,
<anna@kernel.org>, <chuck.lever@oracle.com>, <jlayton@kernel.org>,
<neilb@suse.de>, <okorniev@redhat.com>, <Dai.Ngo@oracle.com>,
<tom@talpey.com>, <davem@davemloft.net>, <edumazet@google.com>,
<kuba@kernel.org>, <pabeni@redhat.com>, <paul@paul-moore.com>,
<jmorris@namei.org>, <linux-sh@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<linux-mm@kvack.org>, <linux-nfs@vger.kernel.org>,
<netdev@vger.kernel.org>, <linux-security-module@vger.kernel.org>,
<wangkefeng.wang@huawei.com>
Subject: Re: [PATCH v2 -next 00/15] sysctl: move sysctls from vm_table into its own files
Date: Fri, 6 Sep 2024 10:35:08 +0800 [thread overview]
Message-ID: <0a12953b-0d11-00d2-ef0e-454d0e3d98f3@huawei.com> (raw)
In-Reply-To: <20240903203837.cbzs3ziuh6eq4kvo@joelS2.panther.com>
On 2024/9/4 4:38, Joel Granados wrote:
> On Tue, Sep 03, 2024 at 11:29:56AM +0800, Kaixiong Yu wrote:
>> This patch series moves sysctls of vm_table in kernel/sysctl.c to
>> places where they actually belong, and do some related code clean-ups.
>> After this patch series, all sysctls in vm_table have been moved into its
>> own files, meanwhile, delete vm_table.
>>
>> All the modifications of this patch series base on
>> linux-next(tags/next-20240902). To test this patch series, the code was
>> compiled with both the CONFIG_SYSCTL enabled and disabled on arm64 and
>> x86_64 architectures. After this patch series is applied, all files
>> under /proc/sys/vm can be read or written normally.
> This move make a lot of sense. The question with these multi-subsystem
> patchsets is how do they go into mainline. For now I have added this to
> sysctl-testing to see if it needs more work. I can push this through the
> sysctl subsystem, but you need to get reviewed-by for all of the commits
> in different subsystems. I'm also fine with this going in through some
> other subsys if anyone wants to take it?
>
> Best
>
Thx，Joel!:-)
Hello，everyone!
This patch series has been reviewed by Kees, Jan Kara, Christian
Brauner, and acked
by Anna Schumaker, Paul Moore. As Joel said, this patch series need to
get reviewed-by
for all of the commits in different subsystems. I would appreciate it if
you could review
this patch series as soon as possible !:-)
prev parent reply other threads:[~2024-09-06 2:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240903033105eucas1p2b9d0b874da268fecb49905d90340de09@eucas1p2.samsung.com>
2024-09-03 3:29 ` [PATCH v2 -next 00/15] sysctl: move sysctls from vm_table into its own files Kaixiong Yu
2024-09-03 3:29 ` [PATCH v2 -next 01/15] mm: vmstat: move sysctls to " Kaixiong Yu
2024-09-03 3:29 ` [PATCH v2 -next 02/15] mm: filemap: move sysctl to its own file Kaixiong Yu
2024-09-03 3:29 ` [PATCH v2 -next 03/15] mm: swap: " Kaixiong Yu
2024-09-03 3:30 ` [PATCH v2 -next 04/15] mm: vmscan: move vmscan sysctls " Kaixiong Yu
2024-09-03 3:30 ` [PATCH v2 -next 05/15] mm: util: move sysctls into it own files Kaixiong Yu
2024-09-03 3:30 ` [PATCH v2 -next 06/15] mm: mmap: move sysctl into its own file Kaixiong Yu
2024-09-03 3:30 ` [PATCH v2 -next 07/15] security: min_addr: " Kaixiong Yu
2024-09-03 16:31 ` Paul Moore
2024-09-03 3:30 ` [PATCH v2 -next 08/15] mm: nommu: move sysctl to " Kaixiong Yu
2024-09-03 3:30 ` [PATCH v2 -next 09/15] fs: fs-writeback: " Kaixiong Yu
2024-09-03 3:30 ` [PATCH v2 -next 10/15] fs: drop_caches: " Kaixiong Yu
2024-09-03 3:30 ` [PATCH v2 -next 11/15] sunrpc: use vfs_pressure_ratio() helper Kaixiong Yu
2024-09-04 19:45 ` Anna Schumaker
2024-09-03 3:30 ` [PATCH v2 -next 12/15] fs: dcache: move the sysctl into its own file Kaixiong Yu
2024-09-03 3:30 ` [PATCH v2 -next 13/15] x86: vdso: " Kaixiong Yu
2024-09-03 3:30 ` [PATCH v2 -next 14/15] sh: " Kaixiong Yu
2024-09-03 3:30 ` [PATCH v2 -next 15/15] sysctl: remove unneeded include Kaixiong Yu
2024-09-03 20:38 ` [PATCH v2 -next 00/15] sysctl: move sysctls from vm_table into its own files Joel Granados
2024-09-06 2:35 ` yukaixiong [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=0a12953b-0d11-00d2-ef0e-454d0e3d98f3@huawei.com \
--to=yukaixiong@huawei.com \
--cc="wangkefeng.wang@huawei.com liushixin2@huawei.com liuyongqiang13@huawei.com tongtiangen@huawei.com sunnanyong@huawei.com mawupeng1@huawei.com zuoze1@huawei.com zhangpeng362@huawei.com tujinjiang@huawei.com yaolulu5"@huawei.com \
--cc=Dai.Ngo@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=anna@kernel.org \
--cc=bp@alien8.de \
--cc=brauner@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dalias@libc.org \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=guohanjun@huawei.com \
--cc=hpa@zytor.com \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=jmorris@namei.org \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=luto@kernel.org \
--cc=neilb@suse.de \
--cc=netdev@vger.kernel.org \
--cc=okorniev@redhat.com \
--cc=pabeni@redhat.com \
--cc=paul@paul-moore.com \
--cc=tglx@linutronix.de \
--cc=tom@talpey.com \
--cc=trondmy@kernel.org \
--cc=vbabka@suse.cz \
--cc=viro@zeniv.linux.org.uk \
--cc=wangkefeng.wang@huawei.com \
--cc=willy@infradead.org \
--cc=ysato@users.osdn.me \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).