From: Ralf Baechle <ralf@linux-mips.org>
To: James Cowgill <James.Cowgill@imgtec.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH 1/2] MIPS: opt into HAVE_COPY_THREAD_TLS
Date: Mon, 10 Apr 2017 13:19:22 +0200 [thread overview]
Message-ID: <20170410111922.GF24214@linux-mips.org> (raw)
In-Reply-To: <20170331160959.3192-2-James.Cowgill@imgtec.com>
Thanks, applied.
Ralf
next prev parent reply other threads:[~2017-04-10 11:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 16:09 [PATCH 0/2] Fix indirect syscall handler for syscalls with > 4 args James Cowgill
2017-03-31 16:09 ` James Cowgill
2017-03-31 16:09 ` [PATCH 1/2] MIPS: opt into HAVE_COPY_THREAD_TLS James Cowgill
2017-03-31 16:09 ` James Cowgill
2017-04-10 11:19 ` Ralf Baechle [this message]
2017-03-31 16:09 ` [PATCH 2/2] MIPS: Remove pt_regs adjustments in indirect syscall handler James Cowgill
2017-03-31 16:09 ` James Cowgill
2017-07-17 14:27 ` James Cowgill
2017-07-17 14:27 ` James Cowgill
2017-07-28 14:03 ` James Hogan
2017-07-28 14:03 ` James Hogan
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=20170410111922.GF24214@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=James.Cowgill@imgtec.com \
--cc=linux-mips@linux-mips.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;
as well as URLs for NNTP newsgroup(s).