public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>, George Anzinger <george@mvista.com>
Cc: linux-kernel@vger.kernel.org, Roland McGrath <roland@redhat.com>
Subject: [-mm patch] kernel/signal.c: fix compile warning
Date: Fri, 18 Nov 2005 02:41:02 +0100	[thread overview]
Message-ID: <20051118014102.GL11494@stusta.de> (raw)
In-Reply-To: <20051117111807.6d4b0535.akpm@osdl.org>

On Thu, Nov 17, 2005 at 11:18:07AM -0800, Andrew Morton wrote:
>...
> Changes since 2.6.14-mm2:
>...
> +sigaction-should-clear-all-signals-on-sig_ign-not-just.patch
> 
>  Signal code fix
>...


Patches get bonus points when they don't introduce new compile 
warnings...

<--  snip  -->

...
  CC      kernel/signal.o
kernel/signal.c: In function 'rm_from_queue_full':
kernel/signal.c:638: warning: control may reach end of non-void function 'sigisemptyset' being inlined
...

<--  snip  -->


Signed-off-by: Adrian Bunk <bunk@stusta.de>

--- linux-2.6.15-rc1-mm1-full/include/linux/signal.h.old	2005-11-18 00:47:49.000000000 +0100
+++ linux-2.6.15-rc1-mm1-full/include/linux/signal.h	2005-11-18 00:52:13.000000000 +0100
@@ -102,6 +102,7 @@
 		return set->sig[0] == 0;
 	default:
 		_NSIG_WORDS_is_unsupported_size();
+		return 0;
 	}
 }
 


  parent reply	other threads:[~2005-11-18  1:41 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17 19:18 2.6.15-rc1-mm1 Andrew Morton
2005-11-17 21:30 ` 2.6.15-rc1-mm1 Valdis.Kletnieks
2005-11-17 22:14   ` 2.6.15-rc1-mm1 David Howells
2005-11-17 22:23     ` 2.6.15-rc1-mm1 Valdis.Kletnieks
2005-11-18  4:23       ` 2.6.15-rc1-mm1 - immediate system reset at boot Valdis.Kletnieks
2005-11-18  4:27         ` Andrew Morton
2005-11-18  1:41 ` Adrian Bunk [this message]
2005-11-18  3:59   ` [-mm patch] kernel/signal.c: fix compile warning George Anzinger
2005-11-18  1:44 ` 2.6.15-rc1-mm1 Richard Knutsson
2005-11-18  1:53   ` 2.6.15-rc1-mm1 Andrew Morton
2005-11-18  7:20 ` 2.6.15-rc1-mm1 Reuben Farrelly
2005-11-18  7:42   ` 2.6.15-rc1-mm1 Andrew Morton
2005-11-18  7:56     ` 2.6.15-rc1-mm1 Sander
2005-11-18 20:58     ` 2.6.15-rc1-mm1 Reuben Farrelly
2005-11-18 21:19       ` 2.6.15-rc1-mm1 Andrew Morton
2005-11-18 12:43 ` 2.6.15-rc1-mm1 Ed Tomlinson
2005-11-18 20:37   ` 2.6.15-rc1-mm1 Greg KH
2005-11-18 21:14     ` 2.6.15-rc1-mm1 Ian McDonald
2005-11-18 23:16       ` 2.6.15-rc1-mm1 Ed Tomlinson
2005-11-18 23:03         ` 2.6.15-rc1-mm1 Greg KH
2005-11-18 23:35         ` 2.6.15-rc1-mm1 Ed Tomlinson
2005-11-18 23:51           ` 2.6.15-rc1-mm1 Greg KH
2005-11-19  1:24             ` 2.6.15-rc1-mm1 Ed Tomlinson
2005-11-19  1:26               ` 2.6.15-rc1-mm1 Greg KH
2005-11-19  1:49                 ` 2.6.15-rc1-mm1 Ian McDonald
2005-11-19  3:24                 ` 2.6.15-rc1-mm1 Ed Tomlinson
2005-11-21  0:00                   ` 2.6.15-rc1-mm1 Ian McDonald
2005-11-21  0:26                   ` 2.6.15-rc1-mm1 Greg KH
2005-11-22 20:47                     ` 2.6.15-rc1-mm1 Ian McDonald
2005-11-22 20:55                       ` 2.6.15-rc1-mm1 Greg KH
2005-11-22 22:05                         ` 2.6.15-rc1-mm1 Ian McDonald
2005-11-19  1:40               ` 2.6.15-rc1-mm1 Ian McDonald

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=20051118014102.GL11494@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=george@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@redhat.com \
    /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