From: Christoph Hellwig <hch@infradead.org>
To: Andrew Morton <akpm@zip.com.au>
Cc: Dave Jones <davej@suse.de>,
kernel-janitor-discuss@lists.sourceforge.net, linux-mm@kvack.org
Subject: Re: page-flags.h
Date: Fri, 3 May 2002 09:24:36 +0100 [thread overview]
Message-ID: <20020503092436.A19267@infradead.org> (raw)
In-Reply-To: <3CD1FB78.B3314F4B@zip.com.au>; from akpm@zip.com.au on Thu, May 02, 2002 at 07:52:40PM -0700
On Thu, May 02, 2002 at 07:52:40PM -0700, Andrew Morton wrote:
> > That's a good point, and something I completley overlooked.
> > I wonder if Andrew Morton (who I'm guessing wrote that comment
> > in mm.h) has some ingenious plan here..
>
> who, me?
>
> I'd envisaged those 119 files doing:
>
> #include <linux/mm.h>
> #include <linux/page-flags.h>
>
> so then anything which includes mm.h but doesn't do any PageFoo()
> operations doesn't have to process those macros.
Okay, that makes some sense. I still think it's preferrable to
have <linux/page.h> - many filesystems only need struct page, the
flags and few supporting functions, so do drivers using kiobufs.
Having these no need the rest of the MM internals is a good thing (TM).
--
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/
next prev parent reply other threads:[~2002-05-03 8:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020501192737.R29327@suse.de>
2002-05-01 17:34 ` page-flags.h Christoph Hellwig
2002-05-01 18:04 ` page-flags.h Dave Jones
2002-05-03 2:52 ` page-flags.h Andrew Morton
2002-05-03 8:24 ` Christoph Hellwig [this message]
2002-05-03 22:41 ` page-flags.h Erik van Konijnenburg
2002-05-03 23:06 ` page-flags.h Andrew Morton
2002-05-03 23:39 ` page-flags.h Dave Jones
2002-05-04 6:46 ` page-flags.h Erik van Konijnenburg
2002-05-14 20:25 ` page-flags.h Andrew Morton
2002-05-15 12:38 ` page-flags.h Christoph Hellwig
2002-08-29 19:04 ` page-flags.h Daniel Phillips
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=20020503092436.A19267@infradead.org \
--to=hch@infradead.org \
--cc=akpm@zip.com.au \
--cc=davej@suse.de \
--cc=kernel-janitor-discuss@lists.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox