From: Ralf Baechle <ralf@linux-mips.org>
To: "Steven J. Hill" <sjhill@realitydiluted.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Ideas on removing a compiler warning in 'init_task.c' ...
Date: Tue, 21 Dec 2004 01:25:06 +0100 [thread overview]
Message-ID: <20041221002506.GA6538@linux-mips.org> (raw)
In-Reply-To: <41C377ED.1040502@realitydiluted.com>
On Fri, Dec 17, 2004 at 06:21:01PM -0600, Steven J. Hill wrote:
> I actually broke out the macro and it is complaining about the
> initialization
> of 'action' member in the 'sighand_struct' defined in
> 'include/linux/sched.h'.
>
> struct sighand_struct {
> atomic_t count;
> struct k_sigaction action[_NSIG];
> spinlock_t siglock;
> };
>
> I do not see this when compiling x86 code and the MIPS structure is
> not that drastically different IMHO. Anyone have some ideas on this
> one?
The members of struct sigaction are ordered differently on MIPS.
Ralf
prev parent reply other threads:[~2004-12-21 0:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-18 0:21 Ideas on removing a compiler warning in 'init_task.c' Steven J. Hill
2004-12-21 0:25 ` Ralf Baechle [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=20041221002506.GA6538@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=sjhill@realitydiluted.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