Re: [PATCH v4 -next 00/15] sysctl: move sysctls from vm_table into its own files
yukaixiong <[email protected]>
| Newsgroups | gmane.linux.kernel.lsm,gmane.linux.ports.sh.devel,gmane.linux.kernel,gmane.linux.file-systems,gmane.linux.kernel.mm,gmane.linux.nfs,gmane.linux.network |
|---|---|
| Message-ID | <[email protected]> |
On 2025/1/6 19:22, Joel Granados wrote: > On Sat, Dec 28, 2024 at 09:40:50PM +0800, yukaixiong wrote: >> >> On 2024/12/28 20:15, Joel Granados wrote: >>> On Mon, Dec 23, 2024 at 10:15:19PM +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. > ... >>>> sysctl: remove unneeded include >>> This patchset looks strange. There seems to be 15 patches, but there are >>> 30 e-mails in the thread? You can also see this when you look at it in >>> lore [1]. And they are different repeated e-mails (mutt does not >>> de-duplicate them). Also `b4 shazam ...` does not work. What happened? >>> Did you send it twice with the same mail ID? Am I the only one seeing >>> this? >>> >>> I would suggest the following (hopefully you are using b4): >>> 1. Check to see how things will be sent with b4. `b4 send --resend -o OUTPUT_DIR` >>> If you see 30 emails in that dir from your patchset then something is >>> still wrong. >>> 2. After you make sure that everything is in order. Do the resend >>> without bumping the version up (leave it at version 4) >>> >>> Best >>> >>> [1] : https://lore.kernel.org/all/[email protected]/ >> I'm very sorry, due to my mistake, 15 patches were sent twice. > No worries. I saw that you have re-sent the patchset and it seems that > this time there is only 15 mails. I see that you are only using my > [email protected] ID; can you please add my kernel.org > ([email protected]) mail to the future mails that you send (no > need to re-send v4). > > Thx > > ... OK, I will add [email protected] to the future mails.