From: George Anzinger <george@mvista.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Roland McGrath <roland@redhat.com>
Subject: Re: [-mm patch] kernel/signal.c: fix compile warning
Date: Thu, 17 Nov 2005 19:59:54 -0800 [thread overview]
Message-ID: <437D51BA.60608@mvista.com> (raw)
In-Reply-To: <20051118014102.GL11494@stusta.de>
Adrian Bunk wrote:
> 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...
Even more when the fix them. My loss, your gain :). Still I wonder
why I did not see that.
George
--
--
George Anzinger george@mvista.com
HRT (High-res-timers): http://sourceforge.net/projects/high-res-timers/
next prev parent reply other threads:[~2005-11-18 4:02 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 ` [-mm patch] kernel/signal.c: fix compile warning Adrian Bunk
2005-11-18 3:59 ` George Anzinger [this message]
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=437D51BA.60608@mvista.com \
--to=george@mvista.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--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 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.