All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Christoph Hellwig <hch@sgi.com>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] allow CONFIG_SWAP=n for i386
Date: Wed, 26 Feb 2003 14:40:15 -0800	[thread overview]
Message-ID: <20030226144015.54ebcbcc.akpm@digeo.com> (raw)
In-Reply-To: <20030227005100.B15460@sgi.com>

Christoph Hellwig <hch@sgi.com> wrote:
>
> On Wed, Feb 26, 2003 at 02:20:24PM -0800, Andrew Morton wrote:
> > > There's a bunch of minor fixes needed to disable the swap
> > > code for systems with mmu.
> > 
> > A worthy objective.
> > 
> > > +	.i_shared_sem	= __MUTEX_INITIALIZER(&swapper_space.i_shared_sem),
> > 
> > arch/um des not have __MUTEX_INITIALIZER, and I'm not sure that we want to
> > promote this to part of the kernel API, do we?
> > 
> > Might be better to leave that bit alone.  Maybe stick an initcall into
> > swap_state.c for it.
> 
> Personally I'd prefer to use __MUTEX_INITIALIZER because we really need
> a way to intialize a semaphore at compile time.  Would either using
> __SEMAPHORE_INITIALIZER() or renaming one of them to something more sane
> be okay with you?

Actually I think I misread the UML code - seems that it just includes
the host architecture's semaphore.h, so what you have should be fine.
I'll queue it up.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>

  reply	other threads:[~2003-02-26 22:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-27  5:21 [PATCH] allow CONFIG_SWAP=n for i386 Christoph Hellwig
2003-02-26 22:20 ` Andrew Morton
2003-02-27  5:51   ` Christoph Hellwig
2003-02-26 22:40     ` Andrew Morton [this message]
2003-02-26 23:04 ` Andrew Morton
2003-02-26 23:36   ` Christoph Hellwig
     [not found] <200303030506.h2356Z627107@hera.kernel.org>
2003-03-03  9:57 ` Geert Uytterhoeven

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=20030226144015.54ebcbcc.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=hch@sgi.com \
    --cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.