From: Michael Ellerman <mpe@ellerman.id.au>
To: Jiri Slaby <jslaby@suse.cz>, akpm@linux-foundation.org
Cc: linux-mips@linux-mips.org, linux-s390@vger.kernel.org,
Rich Felker <dalias@libc.org>,
Aurelien Jacquiot <a-jacquiot@ti.com>,
Peter Zijlstra <peterz@infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
David Howells <dhowells@redhat.com>,
Max Filippov <jcmvbkbc@gmail.com>,
Paul Mackerras <paulus@samba.org>,
"H. Peter Anvin" <hpa@zytor.com>,
sparclinux@vger.kernel.org, linux-hexagon@vger.kernel.org,
Guan Xuetao <gxt@mprc.pku.edu.cn>, Jiri Slaby <jslaby@suse.cz>,
Lennox Wu <lennox.wu@gmail.com>,
Hans-Christian Egtvedt <egtvedt@samfundet.no>,
Jonas Bonn <jonas@southpole.se>,
Chen Liqin <liqin.linux@gmail.com>,
Jesper Nilsson <jesper.nilsson@axis.com>,
linux-am33-list@redhat.com, Russell King <linux@arm.linux.org.uk>,
linux-c6x-dev@linux-c6, x.org,
Yoshinori Sato <ysato@users.sourceforge.jp>,
linux-sh@vger.kernel.org, Helge Deller <deller@gmx>
Subject: Re: [3/4] exit_thread: accept a task parameter to be exited
Date: Fri, 25 Mar 2016 19:32:11 +1100 (AEDT) [thread overview]
Message-ID: <3qWc3w0GCtz9sdm@ozlabs.org> (raw)
In-Reply-To: <1458824294-29733-1-git-send-email-jslaby@suse.cz>
On Thu, 2016-24-03 at 12:58:13 UTC, Jiri Slaby wrote:
> We need to call exit_thread from copy_process in a fail path. So make
> it accept task_struct as a parameter.
If I'm counting right 22 of those are empty functions, so would it be a good
clean up to make it optional first?
cheers
prev parent reply other threads:[~2016-03-25 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 12:58 [PATCH 3/4] exit_thread: accept a task parameter to be exited Jiri Slaby
2016-03-24 13:03 ` Peter Zijlstra
2016-03-24 13:05 ` Jiri Slaby
2016-03-24 15:36 ` Russell King - ARM Linux
2016-03-25 8:32 ` Michael Ellerman [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=3qWc3w0GCtz9sdm@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=a-jacquiot@ti.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=dalias@libc.org \
--cc=deller@gmx \
--cc=dhowells@redhat.com \
--cc=egtvedt@samfundet.no \
--cc=gxt@mprc.pku.edu.cn \
--cc=hpa@zytor.com \
--cc=jcmvbkbc@gmail.com \
--cc=jesper.nilsson@axis.com \
--cc=jonas@southpole.se \
--cc=jslaby@suse.cz \
--cc=lennox.wu@gmail.com \
--cc=linux-am33-list@redhat.com \
--cc=linux-c6x-dev@linux-c6 \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=liqin.linux@gmail.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=sparclinux@vger.kernel.org \
--cc=will.deacon@arm.com \
--cc=ysato@users.sourceforge.jp \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).