From: Stafford Horne <shorne@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>,
Openrisc <openrisc@lists.librecores.org>
Cc: Stafford Horne <shorne@gmail.com>,
Christian Brauner <christian@brauner.io>
Subject: [PATCH 0/3] OpenRISC clone3 support
Date: Thu, 27 Feb 2020 07:56:22 +0900 [thread overview]
Message-ID: <20200226225625.28935-1-shorne@gmail.com> (raw)
This series fixes the clone3 not implemented warnings I have been seeing
during recent builds. It was a simple case of implementing copy_thread_tls
and turning on clone3 generic support. Testing shows no issues.
Stafford Horne (3):
openrisc: Convert copy_thread to copy_thread_tls
openrisc: Enable the clone3 syscall
openrisc: Cleanup copy_thread_tls docs and comments
arch/openrisc/Kconfig | 1 +
arch/openrisc/include/uapi/asm/unistd.h | 1 +
arch/openrisc/kernel/process.c | 19 +++++++------------
3 files changed, 9 insertions(+), 12 deletions(-)
--
2.21.0
next reply other threads:[~2020-02-26 22:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 22:56 Stafford Horne [this message]
2020-02-26 22:56 ` [PATCH 1/3] openrisc: Convert copy_thread to copy_thread_tls Stafford Horne
2020-02-27 0:31 ` Stafford Horne
2020-02-27 12:19 ` Christian Brauner
2020-02-27 13:16 ` Stafford Horne
2020-02-26 22:56 ` [PATCH 2/3] openrisc: Enable the clone3 syscall Stafford Horne
2020-02-27 12:21 ` Christian Brauner
2020-02-27 13:29 ` Stafford Horne
2020-02-26 22:56 ` [PATCH 3/3] openrisc: Cleanup copy_thread_tls docs and comments Stafford Horne
2020-02-27 12:24 ` Christian Brauner
2020-02-27 12:26 ` [PATCH 0/3] OpenRISC clone3 support Christian Brauner
2020-02-27 13:18 ` Stafford Horne
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=20200226225625.28935-1-shorne@gmail.com \
--to=shorne@gmail.com \
--cc=christian@brauner.io \
--cc=linux-kernel@vger.kernel.org \
--cc=openrisc@lists.librecores.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