public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@cyclades.com>
To: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Cc: Christoph Lameter <christoph@lameter.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH] try_to_freeze call fixes.
Date: Mon, 18 Jul 2005 13:36:48 +1000	[thread overview]
Message-ID: <1121657807.13493.47.camel@localhost> (raw)

Hi all.

Here are fixes for four try_to_freeze calls that are still (incorrectly)
using a parameter after the recent try_to_freeze() changes.

Regards,

Nigel

Signed-Off by: Nigel Cunningham <nigel@suspend2.net>

 mips/kernel/irixsig.c  |    2 +-
 mips/kernel/signal32.c |    2 +-
 sh/kernel/signal.c     |    2 +-
 sh64/kernel/signal.c   |    2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)
diff -ruNp 202-more-try-to-freeze.patch-old/arch/mips/kernel/irixsig.c 202-more-try-to-freeze.patch-new/arch/mips/kernel/irixsig.c
--- 202-more-try-to-freeze.patch-old/arch/mips/kernel/irixsig.c	2005-06-20 11:46:44.000000000 +1000
+++ 202-more-try-to-freeze.patch-new/arch/mips/kernel/irixsig.c	2005-07-09 20:41:44.000000000 +1000
@@ -178,7 +178,7 @@ asmlinkage int do_irix_signal(sigset_t *
 	if (!user_mode(regs))
 		return 1;
 
-	if (try_to_freeze(0))
+	if (try_to_freeze())
 		goto no_signal;
 
 	if (!oldset)
diff -ruNp 202-more-try-to-freeze.patch-old/arch/mips/kernel/signal32.c 202-more-try-to-freeze.patch-new/arch/mips/kernel/signal32.c
--- 202-more-try-to-freeze.patch-old/arch/mips/kernel/signal32.c	2005-06-20 11:46:44.000000000 +1000
+++ 202-more-try-to-freeze.patch-new/arch/mips/kernel/signal32.c	2005-07-09 20:41:44.000000000 +1000
@@ -774,7 +774,7 @@ int do_signal32(sigset_t *oldset, struct
 	if (!user_mode(regs))
 		return 1;
 
-	if (try_to_freeze(0))
+	if (try_to_freeze())
 		goto no_signal;
 
 	if (!oldset)
diff -ruNp 202-more-try-to-freeze.patch-old/arch/sh/kernel/signal.c 202-more-try-to-freeze.patch-new/arch/sh/kernel/signal.c
--- 202-more-try-to-freeze.patch-old/arch/sh/kernel/signal.c	2005-06-20 11:46:47.000000000 +1000
+++ 202-more-try-to-freeze.patch-new/arch/sh/kernel/signal.c	2005-07-09 20:41:45.000000000 +1000
@@ -579,7 +579,7 @@ int do_signal(struct pt_regs *regs, sigs
 	if (!user_mode(regs))
 		return 1;
 
-	if (try_to_freeze(0))
+	if (try_to_freeze())
 		goto no_signal;
 
 	if (!oldset)
diff -ruNp 202-more-try-to-freeze.patch-old/arch/sh64/kernel/signal.c 202-more-try-to-freeze.patch-new/arch/sh64/kernel/signal.c
--- 202-more-try-to-freeze.patch-old/arch/sh64/kernel/signal.c	2005-06-20 11:46:47.000000000 +1000
+++ 202-more-try-to-freeze.patch-new/arch/sh64/kernel/signal.c	2005-07-09 20:41:45.000000000 +1000
@@ -697,7 +697,7 @@ int do_signal(struct pt_regs *regs, sigs
 	if (!user_mode(regs))
 		return 1;
 
-	if (try_to_freeze(0))
+	if (try_to_freeze())
 		goto no_signal;
 
 	if (!oldset)

-- 
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
Be amazed that people believe it happened. 


                 reply	other threads:[~2005-07-18 14:15 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=1121657807.13493.47.camel@localhost \
    --to=ncunningham@cyclades.com \
    --cc=akpm@osdl.org \
    --cc=christoph@lameter.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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