From: "Arnd Bergmann" <arnd@arndb.de>
To: "Ludwig Rydberg" <ludwig.rydberg@gaisler.com>,
"David S . Miller" <davem@davemloft.net>,
"Andreas Larsson" <andreas@gaisler.com>,
"Christian Brauner" <brauner@kernel.org>,
shuah <shuah@kernel.org>
Cc: sparclinux@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org,
"John Paul Adrian Glaubitz" <glaubitz@physik.fu-berlin.de>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"schuster.simon@siemens-energy.com"
<schuster.simon@siemens-energy.com>,
"Jessica Clarke" <jrtc27@jrtc27.com>
Subject: Re: [PATCH v2 2/2] sparc: Add architecture support for clone3
Date: Mon, 19 Jan 2026 15:53:25 +0100 [thread overview]
Message-ID: <93510cb7-e398-4af7-896c-5b4a4654598f@app.fastmail.com> (raw)
In-Reply-To: <20260119144753.27945-3-ludwig.rydberg@gaisler.com>
On Mon, Jan 19, 2026, at 15:47, Ludwig Rydberg wrote:
> Add support for the clone3 system call to the SPARC architectures.
>
> The implementation follows the pattern of the original clone syscall.
> However, instead of explicitly calling kernel_clone, the clone3
> handler calls the generic sys_clone3 handler in kernel/fork.
> In case no stack is provided, the parents stack is reused.
>
> The return value convention for clone3 follows the regular kernel return
> value convention (in contrast to the original clone/fork on SPARC).
>
> Closes: https://github.com/sparclinux/issues/issues/10
> Signed-off-by: Ludwig Rydberg <ludwig.rydberg@gaisler.com>
Thanks a lot for addressing this!
Acked-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2026-01-19 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 14:47 [PATCH v2 0/2] " Ludwig Rydberg
2026-01-19 14:47 ` [PATCH v2 1/2] sparc: Synchronize user stack on fork and clone Ludwig Rydberg
2026-01-19 14:47 ` [PATCH v2 2/2] sparc: Add architecture support for clone3 Ludwig Rydberg
2026-01-19 14:53 ` Arnd Bergmann [this message]
2026-01-20 18:36 ` John Paul Adrian Glaubitz
2026-01-26 17:03 ` Andreas Larsson
2026-01-26 17:03 ` [PATCH v2 0/2] " Andreas Larsson
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=93510cb7-e398-4af7-896c-5b4a4654598f@app.fastmail.com \
--to=arnd@arndb.de \
--cc=andreas@gaisler.com \
--cc=brauner@kernel.org \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=jrtc27@jrtc27.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ludwig.rydberg@gaisler.com \
--cc=schuster.simon@siemens-energy.com \
--cc=shuah@kernel.org \
--cc=sparclinux@vger.kernel.org \
/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
all inboxes | Powered by JetHome®