All of lore.kernel.org
 help / color / mirror / Atom feed
From: akpm@linux-foundation.org
To: drepper@redhat.com, mingo@elte.hu, mm-commits@vger.kernel.org
Subject: - tiny-sched_getaffinity-cleanup.patch removed from -mm tree
Date: Wed, 08 Aug 2007 12:08:00 -0700	[thread overview]
Message-ID: <200708081908.l78J80tS025833@imap1.linux-foundation.org> (raw)


The patch titled
     tiny sched_getaffinity cleanup
has been removed from the -mm tree.  Its filename was
     tiny-sched_getaffinity-cleanup.patch

This patch was dropped because it was merged into mainline or a subsystem tree

------------------------------------------------------
Subject: tiny sched_getaffinity cleanup
From: Ulrich Drepper <drepper@redhat.com>

Unless I'm missing something quite tricky here's another tiny cleanup.  The
generated code is not affected (gcc is smart enough) but for people looking
over the code it is just irritating to have the extra conditional.

Signed-off-by: Ulrich Drepper <drepper@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 kernel/sched.c |    4 +---
 1 files changed, 1 insertion(+), 3 deletions(-)

diff -puN kernel/sched.c~tiny-sched_getaffinity-cleanup kernel/sched.c
--- a/kernel/sched.c~tiny-sched_getaffinity-cleanup
+++ a/kernel/sched.c
@@ -4466,10 +4466,8 @@ long sched_getaffinity(pid_t pid, cpumas
 out_unlock:
 	read_unlock(&tasklist_lock);
 	mutex_unlock(&sched_hotcpu_mutex);
-	if (retval)
-		return retval;
 
-	return 0;
+	return retval;
 }
 
 /**
_

Patches currently in -mm which might be from drepper@redhat.com are

git-sched.patch

                 reply	other threads:[~2007-08-08 19:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200708081908.l78J80tS025833@imap1.linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=drepper@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mm-commits@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.