public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: David Weinehall <tao@acc.umu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: linux-2.6.3-uc0 (MMU-less fixups)
Date: Fri, 20 Feb 2004 10:41:36 +1000	[thread overview]
Message-ID: <403557C0.9060603@snapgear.com> (raw)
In-Reply-To: <20040220001524.GL17140@khan.acc.umu.se>

Hi David,

David Weinehall wrote:
>>>How's the status of the 2.0-port of uClinux, btw?  Is it unintrusive
>>>enough to be considered for a 2.0-merge?
>>
>>Hmm, probably not. It is no where near as clean as the 2.6
>>merge. It could be cleaned up, but no one seems to interrested
>>in doing the work.
> 
> 
> Well, if there are users and interest, I could do at least some of the
> work.  Since I've already done some work with 2.0 uClinux, and since I'm
> the 2.0 maintainer, I do have some experience ;-)

There are still users. I was planning on merging in your 2.0.40
code sometime soon, to bring the uClinux 2.0 sources up to date
at the very least. But if you feel like doing it, that would be
good too :-)

Regards
Greg




------------------------------------------------------------------------
Greg Ungerer  --  Chief Software Dude       EMAIL:     gerg@snapgear.com
SnapGear -- a CyberGuard Company            PHONE:       +61 7 3435 2888
825 Stanley St,                             FAX:         +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia         WEB: http://www.SnapGear.com


  reply	other threads:[~2004-02-20  0:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-19  3:21 [PATCH]: linux-2.6.3-uc0 (MMU-less fixups) Greg Ungerer
2004-02-19 10:39 ` David Weinehall
2004-02-19 12:58   ` Greg Ungerer
2004-02-19 13:13     ` David Weinehall
2004-02-20  0:10       ` Greg Ungerer
2004-02-20  0:15         ` David Weinehall
2004-02-20  0:41           ` Greg Ungerer [this message]
2004-02-22 16:12       ` Pavel Machek
2004-02-22 18:47         ` David Weinehall

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=403557C0.9060603@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tao@acc.umu.se \
    /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