linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <christian.brauner@ubuntu.com>
To: Stafford Horne <shorne@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Openrisc <openrisc@lists.librecores.org>,
	Christian Brauner <christian@brauner.io>
Subject: Re: [PATCH v2 0/3] OpenRISC clone3 support
Date: Mon, 2 Mar 2020 08:44:11 +0100	[thread overview]
Message-ID: <20200302074411.p56ctghzllrijrqz@wittgenstein> (raw)
In-Reply-To: <20200301213851.8096-1-shorne@gmail.com>

On Mon, Mar 02, 2020 at 06:38:48AM +0900, Stafford Horne wrote:
> 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

Excellent. I acked all individual patches now. But the whole series:

Acked-by: Christian Brauner <christian.brauner@ubuntu.com>

  parent reply	other threads:[~2020-03-02  7:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-01 21:38 [PATCH v2 0/3] OpenRISC clone3 support Stafford Horne
2020-03-01 21:38 ` [PATCH v2 1/3] openrisc: Convert copy_thread to copy_thread_tls Stafford Horne
2020-03-02  7:43   ` Christian Brauner
2020-03-01 21:38 ` [PATCH v2 2/3] openrisc: Enable the clone3 syscall Stafford Horne
2020-03-01 21:38 ` [PATCH v2 3/3] openrisc: Cleanup copy_thread_tls docs and comments Stafford Horne
2020-03-02  7:44 ` Christian Brauner [this message]
2020-03-02  9:14   ` [PATCH v2 0/3] OpenRISC clone3 support 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=20200302074411.p56ctghzllrijrqz@wittgenstein \
    --to=christian.brauner@ubuntu.com \
    --cc=christian@brauner.io \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openrisc@lists.librecores.org \
    --cc=shorne@gmail.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).