From: Dave Jones <davej@suse.de>
To: Andrew Morton <akpm@zip.com.au>
Cc: Russell King <rmk@arm.linux.org.uk>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Allow mpage.c to build
Date: Wed, 5 Jun 2002 21:59:27 +0200 [thread overview]
Message-ID: <20020605215927.I16262@suse.de> (raw)
In-Reply-To: <20020605160547.C10293@flint.arm.linux.org.uk> <3CFE6B31.39EC2719@zip.com.au>
On Wed, Jun 05, 2002 at 12:49:05PM -0700, Andrew Morton wrote:
> /usr/src/25/include/linux/bio.h
> /usr/src/25/include/asm/io.h
> /usr/src/25/include/linux/vmalloc.h
> /usr/src/25/include/linux/mm.h
^^^^^
This bugger should be high on the list of include files that need
feeding through the include-chopper-upper.
> /usr/src/25/include/linux/swap.h
> /usr/src/25/include/linux/kdev_t.h
> Lovely, isn't it?
Wouldn't be so bad if it were an isolated case..
Hopefully by the time we get to 2.6, a lot of this
'include by implication' nonsense can be cleaned up some more.
Dave.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
prev parent reply other threads:[~2002-06-05 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-05 15:05 [PATCH] Allow mpage.c to build Russell King
2002-06-05 19:49 ` Andrew Morton
2002-06-05 19:59 ` Dave Jones [this message]
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=20020605215927.I16262@suse.de \
--to=davej@suse.de \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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