From: tip-bot for Li Zefan <lizf@cn.fujitsu.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, dhaval.giani@gmail.com,
hpa@zytor.com, mingo@redhat.com, lizf@cn.fujitsu.com,
peterz@infradead.org, tglx@linutronix.de, mingo@elte.hu
Subject: [tip:sched/core] sched: Remove a stale comment
Date: Mon, 10 May 2010 07:22:07 GMT [thread overview]
Message-ID: <tip-af507ae8a0512a83728b17d8f8c5fa1561669f50@git.kernel.org> (raw)
In-Reply-To: <4BE77C6B.5010402@cn.fujitsu.com>
Commit-ID: af507ae8a0512a83728b17d8f8c5fa1561669f50
Gitweb: http://git.kernel.org/tip/af507ae8a0512a83728b17d8f8c5fa1561669f50
Author: Li Zefan <lizf@cn.fujitsu.com>
AuthorDate: Mon, 10 May 2010 11:24:27 +0800
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Mon, 10 May 2010 08:48:39 +0200
sched: Remove a stale comment
This comment should have been removed together with uids_mutex
when removing user sched.
Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Dhaval Giani <dhaval.giani@gmail.com>
LKML-Reference: <4BE77C6B.5010402@cn.fujitsu.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
kernel/user.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/kernel/user.c b/kernel/user.c
index 8e1c8c0..7e72614 100644
--- a/kernel/user.c
+++ b/kernel/user.c
@@ -136,7 +136,6 @@ struct user_struct *alloc_uid(struct user_namespace *ns, uid_t uid)
struct hlist_head *hashent = uidhashentry(ns, uid);
struct user_struct *up, *new;
- /* Make uid_hash_find() + uid_hash_insert() atomic. */
spin_lock_irq(&uidhash_lock);
up = uid_hash_find(uid, hashent);
spin_unlock_irq(&uidhash_lock);
prev parent reply other threads:[~2010-05-10 7:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 3:24 [PATCH] sched: Remove a bogus comment Li Zefan
2010-05-10 7:22 ` tip-bot for Li Zefan [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=tip-af507ae8a0512a83728b17d8f8c5fa1561669f50@git.kernel.org \
--to=lizf@cn.fujitsu.com \
--cc=dhaval.giani@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome