linux-s390.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vasily Gorbik <gor@linux.ibm.com>
To: Joel Granados <joel.granados@kernel.org>
Cc: Heiko Carstens <hca@linux.ibm.com>, Kees Cook <kees@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	"David S. Miller" <davem@davemloft.net>,
	Andreas Larsson <andreas@gaisler.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	Sven Schnelle <svens@linux.ibm.com>,
	Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
	linux-s390@vger.kernel.org
Subject: Re: [PATCH v2 6/6] s390: mv s390 sysctls into their own file under arch/s390 dir
Date: Tue, 11 Mar 2025 12:02:47 +0100	[thread overview]
Message-ID: <your-ad-here.call-01741690967-ext-1293@work.hours> (raw)
In-Reply-To: <r73ph4ht5ejeeuj65nxocmqp7pury2mekz2lz3r6fs264s24c4@ransymcrzk2h>

On Mon, Mar 10, 2025 at 02:41:59PM +0100, Joel Granados wrote:
> On Fri, Mar 07, 2025 at 04:26:20PM +0100, Heiko Carstens wrote:
> > On Thu, Mar 06, 2025 at 12:29:46PM +0100, joel granados wrote:
> > > Move s390 sysctls (spin_retry and userprocess_debug) into their own
> > > files under arch/s390. We create two new sysctl tables
> > > (2390_{fault,spin}_sysctl_table) which will be initialized with
> > > arch_initcall placing them after their original place in proc_root_init.
> > > 
> > > This is part of a greater effort to move ctl tables into their
> > > respective subsystems which will reduce the merge conflicts in
> > > kernel/sysctl.c.
> > > 
> > > Signed-off-by: joel granados <joel.granados@kernel.org>
> > > ---
> > >  arch/s390/lib/spinlock.c | 18 ++++++++++++++++++
> > >  arch/s390/mm/fault.c     | 17 +++++++++++++++++
> > >  kernel/sysctl.c          | 18 ------------------
> > >  3 files changed, 35 insertions(+), 18 deletions(-)
> > 
> > Acked-by: Heiko Carstens <hca@linux.ibm.com>
> > 
> > How should this go upstream? Will you take care of this, or should
> > this go via the s390 tree?
> 
> thx for the review
> 
> It would be great if you can push it through the s390 tree. However, if
> it is not possible to do so, please let me know and I'll add it to the
> sysctl-next changes.

I've slightly changed the commit message
s390: Move s390 sysctls into their own file under arch/s390

And applied, thank you!

  reply	other threads:[~2025-03-11 11:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-06 11:29 [PATCH v2 0/6] sysctl: Move sysctls from kern_table into their respective subsystems Joel Granados
2025-03-06 11:29 ` [PATCH v2 1/6] panic: Move panic ctl tables into panic.c Joel Granados
2025-03-06 11:29 ` [PATCH v2 2/6] signal: Move signal ctl tables into signal.c Joel Granados
2025-03-06 11:29 ` [PATCH v2 3/6] tracing: Move trace sysctls into trace.c Joel Granados
2025-03-06 11:29 ` [PATCH v2 4/6] stack_tracer: move sysctl registration to kernel/trace/trace_stack.c Joel Granados
2025-03-06 15:31   ` Steven Rostedt
2025-03-13 16:19     ` Joel Granados
2025-03-06 11:29 ` [PATCH v2 5/6] sparc: mv sparc sysctls into their own file under arch/sparc/kernel Joel Granados
2025-03-06 11:29 ` [PATCH v2 6/6] s390: mv s390 sysctls into their own file under arch/s390 dir joel granados
2025-03-07 15:26   ` Heiko Carstens
2025-03-10 13:41     ` Joel Granados
2025-03-11 11:02       ` Vasily Gorbik [this message]
2025-03-13 16:02         ` Joel Granados

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=your-ad-here.call-01741690967-ext-1293@work.hours \
    --to=gor@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=andreas@gaisler.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=davem@davemloft.net \
    --cc=gerald.schaefer@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=joel.granados@kernel.org \
    --cc=kees@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=svens@linux.ibm.com \
    /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 NNTP newsgroup(s).