From: olea@hispafuentes.com
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Cc: juan@hispafuentes.com
Subject: Re: Problems compiling kernel 2.2.17
Date: Wed, 01 Aug 2001 19:35:31 +0200 [thread overview]
Message-ID: <3B683DE3.72CB56F3@hispafuentes.com> (raw)
In-Reply-To: 3B67EDFD.E19F6F6D@hispafuentes.com
Juan and me were talking about our difficult compiling the cvs MTD with
the 2.2.17 kernel must be due to use a wrong cvs branch. Do you maintain
separate developer and stable branchs of MTD?
If not, and if there isn't a dependences conflict in the kernel
.config we can't explain why we can't compile MTD with the nftl support
:-?
--
A.Ismael Olea González
tlf +(34) 914 575 330
mailto:olea@hispafuentes.com
next prev parent reply other threads:[~2001-08-01 17:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 11:08 Problems compiling kernel 2.2.17 Juan Ramon Jimenez Garcia
2001-08-01 11:33 ` Vipin Malik
2001-08-01 11:54 ` olea
2001-08-01 17:35 ` olea [this message]
2001-08-07 9:42 ` David Woodhouse
2001-08-07 9:48 ` David Woodhouse
2001-08-07 11:34 ` Problems compiling kernel 2.2.1-rmk2 Alex Liao
2001-08-07 12:16 ` David Woodhouse
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=3B683DE3.72CB56F3@hispafuentes.com \
--to=olea@hispafuentes.com \
--cc=juan@hispafuentes.com \
--cc=linux-mtd@lists.infradead.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