From: Oleg Nesterov <oleg@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michal Hocko <mhocko@suse.cz>, Sameer Nanda <snanda@chromium.org>,
Sergey Dyasly <dserrg@gmail.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] more next_thread/while_each_thread changes
Date: Fri, 22 Nov 2013 20:18:03 +0100 [thread overview]
Message-ID: <20131122191803.GA16919@redhat.com> (raw)
Trivial, change the remaining next_thread (ab)users to use
while_each_thread().
The last user which should be changed is next_tid(), but we can't
do this now.
__exit_signal() and complete_signal() are fine, they actually need
next_thread() logic.
Oleg.
fs/proc/array.c | 3 +--
kernel/signal.c | 7 +++----
kernel/sys.c | 3 +--
3 files changed, 5 insertions(+), 8 deletions(-)
next reply other threads:[~2013-11-22 19:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 19:18 Oleg Nesterov [this message]
2013-11-22 19:18 ` [PATCH 1/3] proc: change do_task_stat() to use while_each_thread() Oleg Nesterov
2013-11-22 20:15 ` Sameer Nanda
2013-11-22 19:18 ` [PATCH 2/3] k_getrusage() can " Oleg Nesterov
2013-11-22 20:16 ` Sameer Nanda
2013-11-22 19:18 ` [PATCH 3/3] signals: change do_signal_stop/do_sigaction to " Oleg Nesterov
2013-11-22 20:17 ` Sameer Nanda
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=20131122191803.GA16919@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dserrg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=snanda@chromium.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