From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Andreas Schwab <schwab@linux-m68k.org>,
Thorsten Glaser <tg@mirbsd.de>,
linux-kernel@vger.kernel.org, linux-m68k@vger.kernel.org
Subject: Re: Signal patchset
Date: Fri, 7 Jan 2011 20:05:25 +1000 [thread overview]
Message-ID: <4D26E565.6000708@snapgear.com> (raw)
In-Reply-To: <AANLkTi=iddsbRr+N5iLuGBizbFFQ2JN9sgBFC_Q3uA2K@mail.gmail.com>
Hi Geert,
On 07/01/11 06:42, Geert Uytterhoeven wrote:
> On Thu, Dec 16, 2010 at 14:23, Greg Ungerer<gerg@snapgear.com> wrote:
>> On 15/12/10 20:10, Al Viro wrote:
>>> On Sun, Dec 05, 2010 at 12:15:10PM +0100, Geert Uytterhoeven wrote:
>>>
>>>> Unless someone objects, I'm inclined to apply Al's patchset, as it
>>>> improves the
>>>> situation anyway.
>>>>
>>>> OK?
>>>
>>> FWIW, there's an m68knommu counterpart (ACKed by gerg a while ago). The
>>> entire bunch is on ftp.linux.org.uk/pub/people/viro/m68k-signals - both m68k
>>> and m68knommu sets. I don't know how you guys would prefer it done, since
>
> Thx, good the know the nommu part is there, as I don't seem to have it
> in my mailbox.
>
>>> there's a trivial dependency between m68k and m68knommu parts of series -
>>> the former has
>>> +#ifndef __uClinux__
>>> +#define __ARCH_WANT_SYS_RT_SIGSUSPEND
>>> +#endif
>>> in unistd.h and the latter does
>>> -#ifndef __uClinux__
>>> #define __ARCH_WANT_SYS_RT_SIGSUSPEND
>>> -#endif
>>> Both parts switch to generic sys_rt_sigsuspend(), for mmu and nommu resp.,
>>> so they need __ARCH_WANT_SYS_RT_SIGSUSPEND defined as soon as conversion
>>> is done. Other than that they are independent.
>>
>> I can make sure to send to Linus after Geert. Unless Geert you
>> want to take and send both the m68k and m68knommu changes?
>
> I can take the m68knommu changes with your ack, too.
> I'll try to take a look at it tomorrow...
Acked-by: Greg Ungerer <gerg@uclinux.org>
:-)
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close, FAX: +61 7 3891 3630
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
WARNING: multiple messages have this Message-ID (diff)
From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Andreas Schwab <schwab@linux-m68k.org>,
Thorsten Glaser <tg@mirbsd.de>, <linux-kernel@vger.kernel.org>,
<linux-m68k@vger.kernel.org>
Subject: Re: Signal patchset
Date: Fri, 7 Jan 2011 20:05:25 +1000 [thread overview]
Message-ID: <4D26E565.6000708@snapgear.com> (raw)
In-Reply-To: <AANLkTi=iddsbRr+N5iLuGBizbFFQ2JN9sgBFC_Q3uA2K@mail.gmail.com>
Hi Geert,
On 07/01/11 06:42, Geert Uytterhoeven wrote:
> On Thu, Dec 16, 2010 at 14:23, Greg Ungerer<gerg@snapgear.com> wrote:
>> On 15/12/10 20:10, Al Viro wrote:
>>> On Sun, Dec 05, 2010 at 12:15:10PM +0100, Geert Uytterhoeven wrote:
>>>
>>>> Unless someone objects, I'm inclined to apply Al's patchset, as it
>>>> improves the
>>>> situation anyway.
>>>>
>>>> OK?
>>>
>>> FWIW, there's an m68knommu counterpart (ACKed by gerg a while ago). The
>>> entire bunch is on ftp.linux.org.uk/pub/people/viro/m68k-signals - both m68k
>>> and m68knommu sets. I don't know how you guys would prefer it done, since
>
> Thx, good the know the nommu part is there, as I don't seem to have it
> in my mailbox.
>
>>> there's a trivial dependency between m68k and m68knommu parts of series -
>>> the former has
>>> +#ifndef __uClinux__
>>> +#define __ARCH_WANT_SYS_RT_SIGSUSPEND
>>> +#endif
>>> in unistd.h and the latter does
>>> -#ifndef __uClinux__
>>> #define __ARCH_WANT_SYS_RT_SIGSUSPEND
>>> -#endif
>>> Both parts switch to generic sys_rt_sigsuspend(), for mmu and nommu resp.,
>>> so they need __ARCH_WANT_SYS_RT_SIGSUSPEND defined as soon as conversion
>>> is done. Other than that they are independent.
>>
>> I can make sure to send to Linus after Geert. Unless Geert you
>> want to take and send both the m68k and m68knommu changes?
>
> I can take the m68knommu changes with your ack, too.
> I'll try to take a look at it tomorrow...
Acked-by: Greg Ungerer <gerg@uclinux.org>
:-)
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close, FAX: +61 7 3891 3630
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
next prev parent reply other threads:[~2011-01-07 10:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 11:15 Signal patchset (was: Re: aranym bug, manifests as "ida_remove called for id=13" on recent kernels) Geert Uytterhoeven
2010-12-15 10:10 ` Al Viro
2010-12-16 13:23 ` Signal patchset Greg Ungerer
2010-12-16 13:23 ` Greg Ungerer
2011-01-06 20:42 ` Geert Uytterhoeven
2011-01-07 10:05 ` Greg Ungerer [this message]
2011-01-07 10:05 ` Greg Ungerer
2011-01-07 13:17 ` Geert Uytterhoeven
2011-01-11 0:13 ` Greg Ungerer
2011-01-11 0:13 ` Greg Ungerer
2011-01-01 19:40 ` Thorsten Glaser
2011-01-07 13:21 ` Geert Uytterhoeven
2011-01-09 22:14 ` Thorsten Glaser
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=4D26E565.6000708@snapgear.com \
--to=gerg@snapgear.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schwab@linux-m68k.org \
--cc=tg@mirbsd.de \
--cc=viro@zeniv.linux.org.uk \
/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.