From: Helge Deller <deller@gmx.de>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] a small hunk to cleanup 2 build warning?
Date: Fri, 24 Mar 2006 17:58:27 +0100 [thread overview]
Message-ID: <200603241758.28042.deller@gmx.de> (raw)
In-Reply-To: <IWMZGK$A7E56C1F2E8CACD0CB61C6EEBA1DB197@scarlet.be>
Hello Joel,
thank you for the patch.
I just looked how it is fixed currently in Linus' (>2.6.16) tree, and there this was added to include/linux/compat.h.
Since I don't think we will push the changes you propose to 2.6.16 in the file compat_siginfo.h upstream (since it has been fixed differently), I think it's easier to just stick with this small warning at the moment.
If others here think differently just go ahead...
Regards,
Helge
On Friday 24 March 2006 15:41, Joel Soete wrote:
> Hi pa*,
>
> those 2 warning crossed my look during the build of n4k (64bit) smp kernel (in
> a loop to stress it a bit):
> CC kernel/compat.o
> /usr/src/linux-2.6.16-pa4/kernel/compat.c: In function 'compat_sys_timer_create':
> /usr/src/linux-2.6.16-pa4/kernel/compat.c:531: warning: implicit declaration
> of function 'get_compat_sigevent'
> [...]
> CC ipc/compat_mq.o
> /usr/src/linux-2.6.16-pa4/ipc/compat_mq.c: In function 'compat_sys_mq_notify':
> /usr/src/linux-2.6.16-pa4/ipc/compat_mq.c:113: warning: implicit declaration
> of function 'get_compat_sigevent'
> [...]
>
> imho this simple hunk could be helpfull:
> --- ./include/linux/compat_siginfo.h.Orig 2006-03-24 14:04:10.000000000
> +0100
> +++ ./include/linux/compat_siginfo.h 2006-03-24 14:24:49.000000000 +0100
> @@ -171,6 +171,9 @@
>
> #endif /* !HAVE_ARCH_COMPAT_COPY_SIGINFO */
>
> +extern int get_compat_sigevent(struct sigevent *event,
> + const struct compat_sigevent __user *u_event);
> +
> extern int compat_copy_siginfo_to_user(compat_siginfo_t __user *to, struct
> siginfo *from);
> extern int compat_copy_siginfo_from_user(struct siginfo *to, compat_siginfo_t
> __user *from);
>
> ====<>====
>
> If Ok can you ci?
>
> TIA,
> Joel
>
> -------------------------------------------------------
> NOTE! My email address is changing to ... @scarlet.be
> Please make the necessary changes in your address book.
>
>
>
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
>
>
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2006-03-24 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 14:41 [parisc-linux] a small hunk to cleanup 2 build warning? Joel Soete
2006-03-24 16:58 ` Helge Deller [this message]
2006-03-24 17:17 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2006-03-24 17:39 Joel Soete
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=200603241758.28042.deller@gmx.de \
--to=deller@gmx.de \
--cc=parisc-linux@lists.parisc-linux.org \
/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.