From: Arvind Autar <Autar022@planet.nl>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jason Cox <jpcox@iastate.edu>, "n.v.t n.v.t" <joefso@hotmail.com>
Subject: Re: nicksched v30
Date: Tue, 30 Mar 2004 22:12:25 +0200 [thread overview]
Message-ID: <1080677545.31904.38.camel@debian> (raw)
In-Reply-To: <4068BC7D.2020805@yahoo.com.au>
[-- Attachment #1: Type: text/plain, Size: 507 bytes --]
On Tue, 2004-03-30 at 22:07, n.v.t n.v.t wrote:
> I have been having trouble compiling the -mm kernel 2.6.5-rc3-mm1 with v30.
> Please help.
A friend of mine has been having compile troubles also.
I used this patch to make things compile:
http://www.liquidweb.nl/~arvind/patches/compile-fix.gz
* I don't know if this will breaks things, it seems empirical to me.*
Arvind.
--
Arvind Autar | GnuPG-Key ID: 336E5788
Key fingerprint = FAB8 B3E5 0059 880A 00B8 C859 350E BBDC 336E 5788
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-03-30 20:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 6:38 nicksched v30 Nick Piggin
2004-03-05 10:48 ` Prakash K. Cheemplavam
2004-03-05 11:09 ` Nick Piggin
2004-03-05 12:16 ` Markus Hästbacka
2004-03-05 22:48 ` Mike Fedyk
2004-03-06 3:41 ` Nick Piggin
2004-03-06 11:39 ` Markus Hästbacka
2004-03-07 0:43 ` Nick Piggin
2004-03-08 10:21 ` Markus Hästbacka
2004-03-06 5:17 ` glennpj
2004-03-26 8:33 ` Prakash K. Cheemplavam
2004-03-29 22:19 ` Arvind Autar
2004-03-30 0:17 ` Nick Piggin
2004-03-30 20:12 ` Arvind Autar [this message]
[not found] ` <b9a78ea2ef3cba17ff7976aa8e5f187d@stdbev.com>
2004-03-30 14:03 ` Arvind Autar
-- strict thread matches above, loose matches on Subject: below --
2004-03-30 19:55 n.v.t n.v.t
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=1080677545.31904.38.camel@debian \
--to=autar022@planet.nl \
--cc=PrakashKC@gmx.de \
--cc=joefso@hotmail.com \
--cc=jpcox@iastate.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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