Re: [PATCH v2 0/9] sysctl: first set of kernel/sysctl cleanups

From: Andrew Morton
Date: Tue Nov 23 2021 - 19:14:55 EST

Next message: Longpeng (Mike, Cloud Infrastructure Service Product Dept.): "RE: [PATCH] cpu/hotplug: Allow the CPU in CPU_UP_PREPARE state to be brought up again."
Previous message: kernel test robot: "Re: [PATCH v2] fs/binfmt_elf: Fix AT_PHDR for unusual ELF files"
In reply to: Luis Chamberlain: "[PATCH v2 6/9] sysctl: use const for typically used max/min proc sysctls"
Next in thread: Luis Chamberlain: "Re: [PATCH v2 0/9] sysctl: first set of kernel/sysctl cleanups"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, 23 Nov 2021 12:23:38 -0800 Luis Chamberlain <mcgrof@xxxxxxxxxx> wrote:

> Since the sysctls are all over the place I can either put up a tree
> to keep track of these changes and later send a pull request to Linus
> or we can have them trickle into Andrew's tree. Let me know what folks
> prefer.

I grabbed. I staged them behind all-of-linux-next, to get visibility
into changes in the various trees which might conflict.

Next message: Longpeng (Mike, Cloud Infrastructure Service Product Dept.): "RE: [PATCH] cpu/hotplug: Allow the CPU in CPU_UP_PREPARE state to be brought up again."
Previous message: kernel test robot: "Re: [PATCH v2] fs/binfmt_elf: Fix AT_PHDR for unusual ELF files"
In reply to: Luis Chamberlain: "[PATCH v2 6/9] sysctl: use const for typically used max/min proc sysctls"
Next in thread: Luis Chamberlain: "Re: [PATCH v2 0/9] sysctl: first set of kernel/sysctl cleanups"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]