[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YhWQ+0qPorcJ/Z8l@bombadil.infradead.org>
Date: Tue, 22 Feb 2022 17:42:19 -0800
From: Luis Chamberlain <mcgrof@...nel.org>
To: Yan Zhu <zhuyan34@...wei.com>
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
kafai@...com, songliubraving@...com, yhs@...com,
john.fastabend@...il.com, kpsingh@...nel.org,
keescook@...omium.org, yzaikin@...gle.com, netdev@...r.kernel.org,
bpf@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, zengweilin@...wei.com,
liucheng32@...wei.com, nixiaoming@...wei.com,
xiechengliang1@...wei.com
Subject: Re: [PATCH] bpf: move the bpf syscall sysctl table to its own module
On Wed, Feb 23, 2022 at 09:35:29AM +0800, Yan Zhu wrote:
> Sysctl table is easier to read under its own module.
Hey Yan, thanks for you patch!
This does not explain how this is being to help with maitenance as
otherwise this makes kernel/sysctl.c hard to maintain and we also
tend to get many conflicts. It also does not explain how all the
filesystem sysctls are not gone and that this is just the next step,
moving slowly the rest of the sysctls. Explaining this in the commit
log will help patch review and subsystem maintainers understand the
conext / logic behind the move.
> Signed-off-by: Yan Zhu <zhuyan34@...wei.com>
I'd be more than happy to take this if bpf folks Ack. To avoid conflicts
I can route this through sysctl-next which is put forward in particular
to avoid conflicts across trees for this effort. Let me know.
Luis
Powered by blists - more mailing lists