From: "Per Jessen" <per@computer.org>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: building 2.4.31 for a non-smp system
Date: Sat, 29 Oct 2005 13:57:32 +0200 [thread overview]
Message-ID: <20051029121019.7A3C51071FC@mail.local.net> (raw)
In-Reply-To: <43635E2A.4010405@computer.org>
On Sat, 29 Oct 2005 13:34:02 +0200, Per Jessen wrote:
>>
>> Please send:
>> - your .config
>
>Attached.
I think you can ignore this report - I've just configured the build from
scratch, and everything is working fine. For the previous build(s) I had used
the .config from the .23 kernel - I thought that would be OK, but it obviously
wasn't.
Per Jessen, Zurich
--
regards,
Per Jessen, Zurich
http://www.spamchek.com - let your spam stop here!
next prev parent reply other threads:[~2005-10-29 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051029112755.C6F8B9801D@mail.local.net>
2005-10-29 11:34 ` building 2.4.31 for a non-smp system Per Jessen
2005-10-29 11:57 ` Per Jessen [this message]
2005-10-29 12:04 ` Willy Tarreau
2005-10-29 14:53 ` Gene Heskett
2005-10-29 12:18 ` Adrian Bunk
2005-10-29 13:58 ` Per Jessen
2005-10-29 8:47 Per Jessen
2005-10-29 11:00 ` Adrian Bunk
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=20051029121019.7A3C51071FC@mail.local.net \
--to=per@computer.org \
--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