From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
linux-m68k@vger.kernel.org,
uClinux list <uclinux-dev@uclinux.org>
Subject: Re: Fix support for console port other than ttyS0 on mcf.c
Date: Thu, 5 Feb 2009 17:36:10 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0902051734500.5127@anakin> (raw)
In-Reply-To: <20090205155700.GO26064@csclub.uwaterloo.ca>
On Thu, 5 Feb 2009, Lennart Sorensen wrote:
> On Thu, Feb 05, 2009 at 04:53:50PM +0100, Geert Uytterhoeven wrote:
> > linux-m68k@lists.linux-m68k.org handles m68k (with MMU) only.
> > uclinux-dev@uclinux.org handles m68knommu.
>
> Oh. I think I got confused by the fact the same arch/m68k/include is
> used for both. so I looked up m68k in MAINTAINERS.
Yeah, we just merged it a few day ago :-)
The goal is to merge arch/m68k{,nommu}, too (eventually)...
> I will start bothering uclinux-dev@uclinux.org instead.
>
> So by uclinux driver you meant m68knommu uclinux driver. I was thinking
> uclibc for some reason.
Yes, m68knommu uclinux driver.
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
next prev parent reply other threads:[~2009-02-05 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090204201518.GH26064@csclub.uwaterloo.ca>
2009-02-04 20:20 ` Fix support for console port other than ttyS0 on mcf.c Lennart Sorensen
[not found] ` <20090204202009.GI26064@csclub.uwaterloo.ca>
2009-02-04 21:00 ` Geert Uytterhoeven
2009-02-05 0:24 ` [uClinux-dev] " Greg Ungerer
2009-02-05 15:27 ` Lennart Sorensen
2009-02-05 15:53 ` Geert Uytterhoeven
2009-02-05 15:57 ` Lennart Sorensen
2009-02-05 16:36 ` Geert Uytterhoeven [this message]
2009-02-05 23:45 ` [uClinux-dev] " Greg Ungerer
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=Pine.LNX.4.64.0902051734500.5127@anakin \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--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