public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@redhat.com>
Subject: Re: Linux 2.5.40-ac1
Date: Thu, 03 Oct 2002 09:38:11 +1000	[thread overview]
Message-ID: <3D9B8363.6030806@snapgear.com> (raw)


Hi Alan,

> Linux 2.5.40-ac1
[snip]
> o	Merge most of ucLinux stuff			(Greg Ungerer)

Woohoo!


> 	| It needs putting somewhere so we can pick over the
> 	| hard bits left
> 	| Q: Wouldn't drivers/char/mem-nommu.c be better

OK, that is easy to do...


> 	| Q: How to do the procfs stuff tidily

Yes. I need to spend some time on this one. Just lots
of little differences...


> 	| Q: Wouldn't it be nicer to move all mm or mmnommu specific ksyms
> 	|    int the relevant mm/*.c file area instead of kernel/ksyms

OK, I have a new patch today that cleans all this up.
I made all the existing ksysms symbols present. It turns out
many where already there in my more recent patches anyway.
A couple needed to be stubbed. The next patch has no diffs
to ksyms at all.


> 	| Q: Why ifdef out overcommit -  its even easier to account on 
> 	|    MMUless and useful info

I was looking over this yesterday too. Should be able to clean this
up a bit.

What do you think about the separate mm/mmnommu directories
at the top level?  Should the mmnommu be merged into mm?

Do you want me to CC you when I put new patches up?

Thanks
Greg


------------------------------------------------------------------------
Greg Ungerer  --  Chief Software Wizard        EMAIL:  gerg@snapgear.com
SnapGear Pty Ltd                               PHONE:    +61 7 3435 2888
825 Stanley St,                                  FAX:    +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia              WEB:   www.SnapGear.com


             reply	other threads:[~2002-10-02 23:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-02 23:38 Greg Ungerer [this message]
2002-10-03 14:17 ` Linux 2.5.40-ac1 Christoph Hellwig
2002-10-03 14:20   ` Alan Cox
2002-10-03 14:51     ` Christoph Hellwig
2002-10-03 15:25       ` Alan Cox
2002-10-03 15:28         ` Christoph Hellwig
2002-10-03 15:31         ` Greg Ungerer
2002-10-03 19:16       ` Rik van Riel
2002-10-03 23:44         ` Greg Ungerer
2002-10-04  0:32           ` Rik van Riel
  -- strict thread matches above, loose matches on Subject: below --
2002-10-03 14:45 Manfred Spraul
2002-10-03 14:50 ` David S. Miller
2002-10-03 15:18   ` Manfred Spraul
2002-10-03 15:15     ` David S. Miller
2002-10-03 15:48     ` Alan Cox
2002-10-03 15:53       ` Manfred Spraul
2002-10-03 15:17 ` Alan Cox
2002-10-03 15:34   ` Manfred Spraul
2002-10-02 22:18 Alan Cox

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=3D9B8363.6030806@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=alan@redhat.com \
    --cc=linux-kernel@vger.kernel.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