From: Stafford Horne <shorne@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH v2 0/3] OpenRISC clone3 support
Date: Mon, 2 Mar 2020 06:38:48 +0900 [thread overview]
Message-ID: <20200301213851.8096-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.
Changes since v1:
- Fix some comments pointed out in reviews
- Add Acks to 2/3 and 3/3 from Christian Brauner
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 | 18 ++++++------------
3 files changed, 8 insertions(+), 12 deletions(-)
--
2.21.0
WARNING: multiple messages have this Message-ID (diff)
From: Stafford Horne <shorne@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Openrisc <openrisc@lists.librecores.org>,
Stafford Horne <shorne@gmail.com>,
Christian Brauner <christian@brauner.io>
Subject: [PATCH v2 0/3] OpenRISC clone3 support
Date: Mon, 2 Mar 2020 06:38:48 +0900 [thread overview]
Message-ID: <20200301213851.8096-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.
Changes since v1:
- Fix some comments pointed out in reviews
- Add Acks to 2/3 and 3/3 from Christian Brauner
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 | 18 ++++++------------
3 files changed, 8 insertions(+), 12 deletions(-)
--
2.21.0
next reply other threads:[~2020-03-01 21:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-01 21:38 Stafford Horne [this message]
2020-03-01 21:38 ` [PATCH v2 0/3] OpenRISC clone3 support Stafford Horne
2020-03-01 21:38 ` [OpenRISC] [PATCH v2 1/3] openrisc: Convert copy_thread to copy_thread_tls Stafford Horne
2020-03-01 21:38 ` Stafford Horne
2020-03-02 7:43 ` [OpenRISC] " Christian Brauner
2020-03-02 7:43 ` Christian Brauner
2020-03-01 21:38 ` [OpenRISC] [PATCH v2 2/3] openrisc: Enable the clone3 syscall Stafford Horne
2020-03-01 21:38 ` Stafford Horne
2020-03-01 21:38 ` [OpenRISC] [PATCH v2 3/3] openrisc: Cleanup copy_thread_tls docs and comments Stafford Horne
2020-03-01 21:38 ` Stafford Horne
2020-03-02 7:44 ` [OpenRISC] [PATCH v2 0/3] OpenRISC clone3 support Christian Brauner
2020-03-02 7:44 ` Christian Brauner
2020-03-02 9:14 ` [OpenRISC] " Stafford Horne
2020-03-02 9:14 ` 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=20200301213851.8096-1-shorne@gmail.com \
--to=shorne@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.