public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: <gregkh@suse.de>
To: error27@gmail.com, 20100315082148.GD18181@bicker,
	a.p.zijlstra@chello.nl, dhaval.giani@gmail.com, efault@gmx.de,
	gregkh@suse.de, kay.sievers@vrfy.org,
	linux-kernel@vger.kernel.org, mingo@elte.hu
Cc: <stable@kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "sched: Remove  some dead code" has been added to the 2.6.32-longterm tree
Date: Tue, 15 Feb 2011 14:51:11 -0800	[thread overview]
Message-ID: <12978102711506@kroah.org> (raw)
In-Reply-To: <1297404285.7865.21.camel@marge.simson.net>


This is a note to let you know that I've just added the patch titled

    sched: Remove  some dead code

to the 2.6.32-longterm tree which can be found at:
    http://www.kernel.org/git/?p=linux/kernel/git/longterm/longterm-queue-2.6.32.git;a=summary

The filename of the patch is:
     sched-remove-some-dead-code.patch
and it can be found in the queue-2.6.32 subdirectory.

If you, or anyone else, feels it should not be added to the 2.6.32 longterm tree,
please let <stable@kernel.org> know about it.


>From efault@gmx.de  Tue Feb 15 14:39:20 2011
From: Dan Carpenter <error27@gmail.com>
Date: Fri, 11 Feb 2011 07:04:45 +0100
Subject: sched: Remove  some dead code
To: Dhaval Giani <dhaval.giani@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Peter Zijlstra <a.p.zijlstra@chello.nl>, Ingo Molnar <mingo@elte.hu>, Greg Kroah-Hartman <gregkh@suse.de>
Message-ID: <1297404285.7865.21.camel@marge.simson.net>


From: Dan Carpenter <error27@gmail.com>

commit 618765801ebc271fe0ba3eca99fcfd62a1f786e1 upstream.

This was left over from "7c9414385e sched: Remove USER_SCHED"

Signed-off-by: Dan Carpenter <error27@gmail.com>
Acked-by: Dhaval Giani <dhaval.giani@gmail.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
LKML-Reference: <20100315082148.GD18181@bicker>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Mike Galbraith <efault@gmx.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

---
 kernel/user.c |    2 --
 1 file changed, 2 deletions(-)

--- a/kernel/user.c
+++ b/kernel/user.c
@@ -170,8 +170,6 @@ struct user_struct *alloc_uid(struct use
 
 	return up;
 
-	put_user_ns(new->user_ns);
-	kmem_cache_free(uid_cachep, new);
 out_unlock:
 	return NULL;
 }


Patches currently in longterm-queue-2.6.32 which might be from error27@gmail.com are


  reply	other threads:[~2011-02-15 22:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10  8:48 [PATCH 01/28] sched: Remove USER_SCHED stable-bot for Dhaval Giani
2011-02-10 18:30 ` Dhaval Giani
2011-02-10 18:35   ` Dhaval Giani
2011-02-11  6:04     ` [PATCH 29/28] sched: Remove some dead code Mike Galbraith
2011-02-15 22:51       ` gregkh [this message]
2011-02-11  6:07     ` [PATCH 30/28] kernel/user.c: add lock release annotation on free_user() Mike Galbraith
2011-02-15 22:51       ` Patch "kernel/user.c: add lock release annotation on free_user()" has been added to the 2.6.32-longterm tree gregkh
2011-02-11  6:08     ` [PATCH 01/28] sched: Remove USER_SCHED Mike Galbraith

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=12978102711506@kroah.org \
    --to=gregkh@suse.de \
    --cc=20100315082148.GD18181@bicker \
    --cc=a.p.zijlstra@chello.nl \
    --cc=dhaval.giani@gmail.com \
    --cc=efault@gmx.de \
    --cc=error27@gmail.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@kernel.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