From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Greg Ungerer <gerg@linux-m68k.org>
Cc: "Amanieu d'Antras" <amanieu@gmail.com>,
Christian Brauner <christian@brauner.io>,
Kars de Jong <jongk@linux-m68k.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-Next <linux-next@vger.kernel.org>
Subject: Re: [PATCH] m68k: Implement copy_thread_tls()
Date: Tue, 14 Jan 2020 10:50:34 +0100 [thread overview]
Message-ID: <CAMuHMdXx8Y2qvqg8tMqrzQJuU9DMgSNryGch3XgrTPyqwrkN=A@mail.gmail.com> (raw)
In-Reply-To: <20200113103040.23661-1-geert@linux-m68k.org>
On Mon, Jan 13, 2020 at 11:30 AM Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> This is required for clone3(), which passes the TLS value through a
> struct rather than a register.
>
> As do_fork() is only available if CONFIG_HAVE_COPY_THREAD_TLS is set,
> m68k_clone() must be changed to call _do_fork() directly.
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> ---
> This is a dependency for the combination of commits
> e8bb2a2a1d51511e ("m68k: Wire up clone3() syscall") in m68k/for-next,
> dd499f7a7e342702 ("clone3: ensure copy_thread_tls is implemented") in
> v5.5-rc6.
Applied and queued for v5.6.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2020-01-14 9:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 10:30 [PATCH] m68k: Implement copy_thread_tls() Geert Uytterhoeven
2020-01-13 10:37 ` Christian Brauner
2020-01-14 1:55 ` Greg Ungerer
2020-01-14 9:50 ` Geert Uytterhoeven [this message]
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='CAMuHMdXx8Y2qvqg8tMqrzQJuU9DMgSNryGch3XgrTPyqwrkN=A@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=amanieu@gmail.com \
--cc=christian@brauner.io \
--cc=gerg@linux-m68k.org \
--cc=jongk@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-next@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).