Linux M68K Architecture development
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Maxim Kuvyrkov <maxim@codesourcery.com>, Greg Ungerer <gerg@uclinux.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
	uClinux development list <uclinux-dev@uclinux.org>
Subject: Re: m68k/for-2.6.34
Date: Sat, 6 Feb 2010 10:44:42 +0100	[thread overview]
Message-ID: <10f740e81002060144l7850f81ftd516600c27a33c7c@mail.gmail.com> (raw)
In-Reply-To: <4B6B33EC.9000102@codesourcery.com>

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?

Gr{oetje,eeting}s,

						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

  reply	other threads:[~2010-02-06  9:44 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   ` Geert Uytterhoeven [this message]
2010-02-06 11:08     ` m68k/for-2.6.34 Greg Ungerer
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=10f740e81002060144l7850f81ftd516600c27a33c7c@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=gerg@uclinux.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=maxim@codesourcery.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox