From: Mike Frysinger <vapier@gentoo.org>
To: Matt Mackall <mpm@selenic.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] stub out is_swap_pte for !MMU
Date: Fri, 8 Feb 2008 16:25:12 -0500 [thread overview]
Message-ID: <200802081625.12893.vapier@gentoo.org> (raw)
In-Reply-To: <1202503750.17934.639.camel@cinder.waste.org>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
On Friday 08 February 2008, Matt Mackall wrote:
> On Fri, 2008-02-08 at 15:02 -0500, Mike Frysinger wrote:
> > With commit 698dd4ba6b12e34e1e432c944c01478c0b2cd773, swap_pte() was
> > moved into view of both MMU and !MMU, but uses functions only provided by
> > MMU. Here we stub out the function for !MMU ports.
>
> I'm not sure if this is right compared to my original patch. Does it
> ever make sense to ask "is this pte a swap entry?" on a machine with no
> MMU? Presumably this also means it has no ptes too, right? In which
> case, it's better to comment the whole function out. Then when someone
> tries to ask the above meaningless question, they get a compile error
> rather than a meaningless answer.
honestly, doesnt matter to me since none of the code that currently utilizes
this function is used in no-mmu context. if you want to just put the whole
thing in CONFIG_MMU, then go for it.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2008-02-08 21:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 20:02 [PATCH] stub out is_swap_pte for !MMU Mike Frysinger
2008-02-08 20:49 ` Matt Mackall
2008-02-08 21:25 ` Mike Frysinger [this message]
2008-02-08 21:41 ` Matt Mackall
2008-02-08 22:05 ` Andrew Morton
2008-02-08 22:19 ` Matt Mackall
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=200802081625.12893.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
/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.