From: Tomas Szepe <szepe@pinerecords.com>
To: Miles Lane <miles@megapathdsl.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
Rik van Riel <riel@conectiva.com.br>,
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Subject: Re: 2.5.27 -- memory.c:50:22: asm/rmap.h: No such file or directory
Date: Sun, 21 Jul 2002 07:39:02 +0200 [thread overview]
Message-ID: <20020721053902.GA13191@louise.pinerecords.com> (raw)
In-Reply-To: <1027215455.1863.42.camel@localhost.localdomain>
> Hmm. Sorry for the noise. I think made a backup
> of 2.5 without running "make mrproper" first.
Your report is actually helpful, not so much to Rik, though. According
to Kai Germaschewski (Subject: Re: piggy broken in 2.5.24 build, Date:
Sat, 22 Jun 2002), "For the current kbuild, you should never need to do
make mrproper, it should always recognize changes and rebuild what's
necessary."
Well, what's the problem, Kai?
T.
next prev parent reply other threads:[~2002-07-21 5:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-21 0:27 2.5.27 -- memory.c:50:22: asm/rmap.h: No such file or directory Miles Lane
2002-07-21 0:34 ` Miles Lane
2002-07-21 0:47 ` Rik van Riel
2002-07-21 1:37 ` Miles Lane
2002-07-21 5:39 ` Tomas Szepe [this message]
2002-07-22 14:31 ` Kai Germaschewski
[not found] <Pine.LNX.4.44L.0207202153190.12241-100000@imladris.surriel.com>
2002-07-21 1:32 ` Miles Lane
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=20020721053902.GA13191@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@megapathdsl.net \
--cc=riel@conectiva.com.br \
/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