From: Jesper Nilsson <jesper.nilsson@axis.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mikael.starvik@axis.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CRIS v10: Correct do_signal to fix oops and clean up signal handling in general.
Date: Mon, 14 Jan 2008 08:51:53 +0100 [thread overview]
Message-ID: <20080114075153.GA3912@axis.com> (raw)
In-Reply-To: <20080111154513.43c0d414.akpm@linux-foundation.org>
On Fri, Jan 11, 2008 at 03:45:13PM -0800, Andrew Morton wrote:
> On Fri, 11 Jan 2008 19:59:24 +0100
> Jesper Nilsson <jesper.nilsson@axis.com> wrote:
>
> > CRIS v10: Correct do_signal to fix oops and clean up signal handling in general.
> >
> > This fixes a kernel panic on boot due to do_signal not being compatible
> > with it's callers.
>
> Please sequence-number patches even if they are unrelated. That will make
> emails like this one easier.
Yes, sorry about that, they should have been sequenced.
> 1: CRIS v10: Correct do_signal to fix oops and clean up signal handling in general.
> 2: CRIS: Define __ARCH_WANT_SYS_RT_SIGSUSPEND in unistd.h for CRIS
> 3: CRIS v10: kernel/time.c needs to include linux/vmstat.h to compile.
> 4: CRIS v10: Driver for ds1302 needs to include cris-specific i2c.h
>
> Patches 3 and 4 were missing your signed-off-by:. I added it.
>
> I queued patches 1, 3 and 4 for 2.6.24 and patch 2 for 2.6.25. Do you agree?
All four should be queued for 2.6.24 since patch 2 is needed if patch 1
is included, otherwise sys_rt_sigsuspend will be undefined causing a
link error.
Thanks!
/^JN - Jesper Nilsson
--
Jesper Nilsson -- jesper.nilsson@axis.com
prev parent reply other threads:[~2008-01-14 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 18:59 [PATCH] CRIS v10: Correct do_signal to fix oops and clean up signal handling in general Jesper Nilsson
2008-01-11 23:45 ` Andrew Morton
2008-01-14 7:51 ` Jesper Nilsson [this message]
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=20080114075153.GA3912@axis.com \
--to=jesper.nilsson@axis.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikael.starvik@axis.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.