linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Joel Granados <joel.granados@kernel.org>
To: yukaixiong <yukaixiong@huawei.com>
Cc: Brian Gerst <brgerst@gmail.com>,
	akpm@linux-foundation.org,  mcgrof@kernel.org,
	ysato@users.sourceforge.jp, dalias@libc.org,
	 glaubitz@physik.fu-berlin.de, luto@kernel.org,
	tglx@linutronix.de, mingo@redhat.com,  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,  j.granados@samsung.com, 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,  dhowells@redhat.com,
	haifeng.xu@shopee.com, baolin.wang@linux.alibaba.com,
	 shikemeng@huaweicloud.com, dchinner@redhat.com,
	bfoster@redhat.com, souravpanda@google.com,  hannes@cmpxchg.org,
	rientjes@google.com, pasha.tatashin@soleen.com, david@redhat.com,
	 ryan.roberts@arm.com, ying.huang@intel.com,
	yang@os.amperecomputing.com,  zev@bewilderbeest.net,
	serge@hallyn.com, vegard.nossum@oracle.com,
	 wangkefeng.wang@huawei.com
Subject: Re: Re: [PATCH v4 -next 13/15] x86: vdso: move the sysctl to arch/x86/entry/vdso/vdso32-setup.c
Date: Mon, 6 Jan 2025 13:14:06 +0100	[thread overview]
Message-ID: <ka6zci6bvgvyvlxf5u5g7ecefpqlrlqxwzdviukonmvtzeed54@fkseedf6ilms> (raw)
In-Reply-To: <3ed73b8d-1080-941b-ce6a-2d742b078193@huawei.com>

On Mon, Dec 30, 2024 at 02:43:12PM +0800, yukaixiong wrote:
> 
> 
> On 2024/12/30 7:05, Brian Gerst wrote:
> > On Sat, Dec 28, 2024 at 10:17 AM Kaixiong Yu <yukaixiong@huawei.com> wrote:
...
> >>          return 0;
> >>   }
> >>   __initcall(ia32_binfmt_init);
> >>   #endif /* CONFIG_SYSCTL */
> >>
> >> -#endif /* CONFIG_X86_64 */
> >
> > Brian Gerst
> > .
> Hello all;
> 
> I want to confirm that I should send a new patch series, such as "PATCH 
> v5 -next", or just modify this patch by
> "git send-email -in-reply-to xxxxx",or the maintainer will fix this issue ?
There are still some outstanding comments (besides this one) to the
series that you must address. This is what I propose:

1. Address the outstanding feedback in the series
2. Wait a couple of more days to see if you get more feedback
3. For your next versions, please include the tags from previous
   reviews; I see that you have not added Lorenzo's reviewed by for
   "[PATCH v4 -next 06/15] mm: mmap: move sysctl to mm/mmap.c" and
   "[PATCH v4 -next 08/15] mm: nommu: move sysctl to mm/nommu.c"
4. Once you have addresses all the issues, Send a V5. If there are still
   issues with this version, then we can cherry-pick the patches that
   are already reviewed into upstream and continue working on the ones
   with issues.

Best

-- 

Joel Granados


  reply	other threads:[~2025-01-06 12:14 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-28 14:57 [PATCH v4 -next 00/15] sysctl: move sysctls from vm_table into its own files Kaixiong Yu
2024-12-28 14:57 ` [PATCH v4 -next 01/15] mm: vmstat: move sysctls to mm/vmstat.c Kaixiong Yu
2024-12-28 14:57 ` [PATCH v4 -next 02/15] mm: filemap: move sysctl to mm/filemap.c Kaixiong Yu
2024-12-28 14:57 ` [PATCH v4 -next 03/15] mm: swap: move sysctl to mm/swap.c Kaixiong Yu
2024-12-28 14:57 ` [PATCH v4 -next 04/15] mm: vmscan: move vmscan sysctls to mm/vmscan.c Kaixiong Yu
2024-12-28 14:57 ` [PATCH v4 -next 05/15] mm: util: move sysctls to mm/util.c Kaixiong Yu
2024-12-28 14:57 ` [PATCH v4 -next 06/15] mm: mmap: move sysctl to mm/mmap.c Kaixiong Yu
2024-12-28 14:57 ` [PATCH v4 -next 07/15] security: min_addr: move sysctl to security/min_addr.c Kaixiong Yu
2024-12-28 14:57 ` [PATCH v4 -next 08/15] mm: nommu: move sysctl to mm/nommu.c Kaixiong Yu
2024-12-28 14:57 ` [PATCH v4 -next 09/15] fs: fs-writeback: move sysctl to fs/fs-writeback.c Kaixiong Yu
2024-12-28 14:57 ` [PATCH v4 -next 10/15] fs: drop_caches: move sysctl to fs/drop_caches.c Kaixiong Yu
2024-12-28 14:57 ` [PATCH v4 -next 11/15] sunrpc: simplify rpcauth_cache_shrink_count() Kaixiong Yu
2024-12-28 15:11   ` Jeff Layton
2024-12-28 14:57 ` [PATCH v4 -next 12/15] fs: dcache: move the sysctl to fs/dcache.c Kaixiong Yu
2024-12-28 14:57 ` [PATCH v4 -next 13/15] x86: vdso: move the sysctl to arch/x86/entry/vdso/vdso32-setup.c Kaixiong Yu
2024-12-29 23:05   ` Brian Gerst
2024-12-30  3:02     ` yukaixiong
2024-12-30  6:43     ` yukaixiong
2025-01-06 12:14       ` Joel Granados [this message]
2025-01-09  2:43         ` yukaixiong
2024-12-28 14:57 ` [PATCH v4 -next 14/15] sh: vdso: move the sysctl to arch/sh/kernel/vsyscall/vsyscall.c Kaixiong Yu
2025-01-03 11:11   ` Geert Uytterhoeven
2025-01-09  2:33     ` yukaixiong
2025-01-06 11:59   ` Joel Granados
2025-01-09  2:40     ` yukaixiong
2024-12-28 14:57 ` [PATCH v4 -next 15/15] sysctl: remove unneeded include Kaixiong Yu
2024-12-28 15:11 ` [PATCH v4 -next 00/15] sysctl: move sysctls from vm_table into its own files Jeff Layton
2024-12-30  2:58   ` yukaixiong
2025-01-06 12:15 ` Joel Granados
2025-01-09  2:50   ` yukaixiong

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=ka6zci6bvgvyvlxf5u5g7ecefpqlrlqxwzdviukonmvtzeed54@fkseedf6ilms \
    --to=joel.granados@kernel.org \
    --cc=Dai.Ngo@oracle.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=anna@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=bfoster@redhat.com \
    --cc=bp@alien8.de \
    --cc=brauner@kernel.org \
    --cc=brgerst@gmail.com \
    --cc=chuck.lever@oracle.com \
    --cc=dalias@libc.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=david@redhat.com \
    --cc=dchinner@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=edumazet@google.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=haifeng.xu@shopee.com \
    --cc=hannes@cmpxchg.org \
    --cc=hpa@zytor.com \
    --cc=j.granados@samsung.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=mcgrof@kernel.org \
    --cc=mingo@redhat.com \
    --cc=neilb@suse.de \
    --cc=netdev@vger.kernel.org \
    --cc=okorniev@redhat.com \
    --cc=pabeni@redhat.com \
    --cc=pasha.tatashin@soleen.com \
    --cc=paul@paul-moore.com \
    --cc=rientjes@google.com \
    --cc=ryan.roberts@arm.com \
    --cc=serge@hallyn.com \
    --cc=shikemeng@huaweicloud.com \
    --cc=souravpanda@google.com \
    --cc=tglx@linutronix.de \
    --cc=tom@talpey.com \
    --cc=trondmy@kernel.org \
    --cc=vbabka@suse.cz \
    --cc=vegard.nossum@oracle.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=wangkefeng.wang@huawei.com \
    --cc=willy@infradead.org \
    --cc=yang@os.amperecomputing.com \
    --cc=ying.huang@intel.com \
    --cc=ysato@users.sourceforge.jp \
    --cc=yukaixiong@huawei.com \
    --cc=zev@bewilderbeest.net \
    /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