From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
uClinux development list <uclinux-dev@uclinux.org>,
Greg Ungerer <gerg@uclinux.org>
Subject: Re: m68k/for-2.6.34
Date: Sat, 06 Feb 2010 21:08:55 +1000 [thread overview]
Message-ID: <4B6D4DC7.7050802@snapgear.com> (raw)
In-Reply-To: <10f740e81002060144l7850f81ftd516600c27a33c7c@mail.gmail.com>
On 02/06/2010 07:44 PM, Geert Uytterhoeven wrote:
> On Thu, Feb 4, 2010 at 21:54, Maxim Kuvyrkov<maxim@codesourcery.com> wrote:
>> On 2/1/10 11:12 PM, Geert Uytterhoeven wrote:
>> ...
>>>
>>> Should I add the NPTL support for m68k and m68knommu, or shall I wait
>>> for 2.6.35?
>>
>> Notwithstanding the bias, I think you should merge the NPTL support. The
>> NPTL changes don't touch any of the existing functionality, they only add
>> the new syscalls, so the risk of breaking something is negligible.
>
> OK for me. Greg, OK for m68knommu, too?
Yep, good for m68knommu too.
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
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
next prev parent reply other threads:[~2010-02-06 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 20:12 m68k/for-2.6.34 Geert Uytterhoeven
2010-02-04 20:54 ` m68k/for-2.6.34 Maxim Kuvyrkov
2010-02-06 9:44 ` m68k/for-2.6.34 Geert Uytterhoeven
2010-02-06 11:08 ` Greg Ungerer [this message]
2010-02-09 11:27 ` m68k/for-2.6.34 Maxim Kuvyrkov
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=4B6D4DC7.7050802@snapgear.com \
--to=gerg@snapgear.com \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=linux-m68k@vger.kernel.org \
--cc=uclinux-dev@uclinux.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.