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: Tue, 11 Jan 2011 10:13:55 +1000 [thread overview]
Message-ID: <4D2BA0C3.7090908@snapgear.com> (raw)
In-Reply-To: <AANLkTik-9r_ZPkzVGowW2xT8h+QtVJ57q3mE6iKsuuVa@mail.gmail.com>
On 07/01/11 23:17, Geert Uytterhoeven wrote:
> On Thu, Jan 6, 2011 at 21:42, Geert Uytterhoeven<geert@linux-m68k.org> 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...
>
> I applied the m68k part to master and for-2.6.38/for-linus.
> In addition, I applied the m68knommu part with Greg's acks added to for-next.
>
> Greg, please let me know if this is OK, so I can send a pull request to Linus
> after it's been cooking one night in linux-next.
Oh, yes, that is ok. (I see the pull request now :-)
I have a bunch of things in linux-next for m68knommu, and we
hit nothing there so I think it is all good.
Regards
Greg
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
--
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close FAX: +61 7 3217 5323
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
prev parent reply other threads:[~2011-01-11 0:17 UTC|newest]
Thread overview: 7+ 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
2011-01-06 20:42 ` Geert Uytterhoeven
2011-01-07 10:05 ` Greg Ungerer
2011-01-07 13:17 ` Geert Uytterhoeven
2011-01-11 0:13 ` Greg Ungerer [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=4D2BA0C3.7090908@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox