public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Greg Ungerer <gerg@snapgear.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]: linux-2.5.42uc1 (MMU-less support)
Date: Tue, 15 Oct 2002 18:16:09 +0100	[thread overview]
Message-ID: <20021015181609.A31647@infradead.org> (raw)
In-Reply-To: <3DAC337D.7010804@snapgear.com>; from gerg@snapgear.com on Wed, Oct 16, 2002 at 01:25:49AM +1000

On Wed, Oct 16, 2002 at 01:25:49AM +1000, Greg Ungerer wrote:
> Hi All,
> 
> An updated uClinux patch is available at:
> 
> http://www.uclinux.org/pub/uClinux/uClinux-2.5.x/linux-2.5.42uc1.patch.gz
> 
> Changelog:
> 
> 1. v850 update

There are a bunch of CVS .#* files left from this one.
v850_defs.h wants updating to the generic generate-asm-offsets.h
mechanism (check the toplevel Makefile)
Please stop the ugly symlink hell with the linker scripts -
we have vmlinux.lds.S for that.
it should read something like:

#include <linux/config.h>
#ifdef BOARD1
#include "board1.lds"
#else
...
#endif

for v850

Could you please explain the rootfs hacks in v850?
I don't think we want those in mainline but rather generic
initrd/initramfs.

Also please remove arch/v850/sim/* - that stuff doesn't
belong into the kernel tree.

> 2. cleaned up mm/page_alloc.c

Why do you put set_page_refs into a header?  Separating it out
looks good to me, but IMHO it should stay in page_alloc.c.
BTW, are you sure that you don't need to set the refs in the
other caller of prep_new_page?  To me it looks like you should
and then you could merge it into prep_new_page.

Also, what is CONFIG_CONTIGUOUS_PAGE_ALLOC doing?  It seems not
fully implemented but adds lots of uglieness :)
CONFIG_NO_MMU_LARGE_ALLOCS might want a saner name, btw
(CONFIG_LARGE_ALLOCS?).

General commets:
- Config.in files have three-space, not two-space indentation
- I don't think you want to keep around the old binfmt_flat
  format when merghin into mainline
- MAX_SHARED_LIBS is never used

  reply	other threads:[~2002-10-15 17:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15 15:25 [PATCH]: linux-2.5.42uc1 (MMU-less support) Greg Ungerer
2002-10-15 17:16 ` Christoph Hellwig [this message]
2002-10-16 14:41   ` Greg Ungerer
2002-10-16 14:48     ` Christoph Hellwig
2002-10-16 15:36       ` Greg Ungerer
2002-11-26  7:46   ` [PATCH] Make some EXPORT_SYMBOLs dependent on CONFIG_MMU Miles Bader
2002-11-26  7:49   ` [PATCH] v850 additions to include/linux/elf.h Miles Bader
2002-11-26 15:41     ` Alan Cox
2002-11-27  1:19       ` Miles Bader
2002-11-27 13:01         ` Alan Cox
2002-11-28  1:20           ` Miles Bader
2002-10-16  5:42 ` [PATCH]: linux-2.5.42uc1 (MMU-less support) Miles Bader
2002-10-16 12:49   ` Greg Ungerer
  -- strict thread matches above, loose matches on Subject: below --
2002-10-16 15:49 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=20021015181609.A31647@infradead.org \
    --to=hch@infradead.org \
    --cc=gerg@snapgear.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