From: Roman Zippel <zippel@linux-m68k.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: missing bit from signal patches
Date: Thu, 30 May 2002 10:04:03 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.21.0205300959050.17583-100000@serv> (raw)
In-Reply-To: <20020530101848.2ac84805.sfr@canb.auug.org.au>
Hi,
On Thu, 30 May 2002, Stephen Rothwell wrote:
> The following should allow the affected architectures to build in
> 2.5.19 as currently there will be two definitions of
> copy_siginfo_to_user.
There are other build problems. m68k doesn't compile, because siginfo_t is
defined after the generic include and the inline functions in there access
that structure. On the other hand I can't put the include after the
definition, as it depends on other defines in the include.
I worked around it with some ugly hacks, but a proper fix would be very
welcome.
bye, Roman
next prev parent reply other threads:[~2002-05-30 8:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 0:18 [PATCH] " Stephen Rothwell
2002-05-30 8:04 ` Roman Zippel [this message]
2002-05-30 12:08 ` Stephen Rothwell
2002-05-30 12:46 ` Roman Zippel
2002-05-30 13:26 ` Stephen Rothwell
2002-05-30 14:16 ` Peter Wächtler
2002-05-30 19:57 ` Roman Zippel
2002-05-31 0:24 ` Stephen Rothwell
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=Pine.LNX.4.21.0205300959050.17583-100000@serv \
--to=zippel@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®