From: "Hans E. Kristiansen" <hans@tropic.net>
To: "Kai Germaschewski" <kai@tp1.ruhr-uni-bochum.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.22 problems with compile.h
Date: Tue, 18 Jun 2002 23:58:03 +0800 [thread overview]
Message-ID: <009601c216e0$fa64f180$1532a8c0@private.tropic.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0206180931410.5695-100000@chaos.physics.uiowa.edu>
I applied your patch which was included in an earlier email on the advice
from Mr. Martin Deal, and it works! Can't ask for more. At last I can go
back to my userland programming.
Perhaps the real problem is that Linus released 2.5.22 on a Monday :)
TTFN,
Hans E.
----- Original Message -----
From: "Kai Germaschewski" <kai@tp1.ruhr-uni-bochum.de>
To: "Hans E. Kristiansen" <hans@tropic.net>
Cc: <linux-kernel@vger.kernel.org>
Sent: Tuesday, June 18, 2002 22:36
Subject: Re: 2.5.22 problems with compile.h
> On Tue, 18 Jun 2002, Hans E. Kristiansen wrote:
>
> > >From a clean install, I can compile, but I get an error with compile.h
(Do
> > not know how to make compile.h). If I compile again, I get a working
kernel
> > (bzImage), "depmod -ae -F xx " works like a charm. But, when I reboot
with
--- snip ----
prev parent reply other threads:[~2002-06-18 15:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 7:27 [PATCH] Push BKL into ->permission() calls Paul Menage
2002-06-18 7:51 ` Andreas Dilger
2002-06-18 8:27 ` Paul Menage
2002-06-18 10:36 ` 2.5.22 problems with compile.h Hans E. Kristiansen
2002-06-18 12:42 ` Martin Diehl
2002-06-18 14:36 ` Kai Germaschewski
2002-06-18 15:58 ` Hans E. Kristiansen [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='009601c216e0$fa64f180$1532a8c0@private.tropic.net' \
--to=hans@tropic.net \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®