From: David Woodhouse <dwmw2@infradead.org>
To: Vipin Malik <vipin@embeddedlinuxworks.com>
Cc: Juan Ramon Jimenez Garcia <juan@hispafuentes.com>,
linux-mtd@lists.infradead.org, olea@hispafuentes.com
Subject: Re: Problems compiling kernel 2.2.17
Date: Tue, 07 Aug 2001 10:42:58 +0100 [thread overview]
Message-ID: <32062.997177378@redhat.com> (raw)
In-Reply-To: <5.1.0.14.0.20010801063242.00a67f20@mail.spewey.com>
vipin@embeddedlinuxworks.com said:
> Don't link in nftl. What do you need this for? You don't need this for
> either DOC OR NOR flash.
NFTL is the translation layer used on the DiskOnChip to emulate a block
device.
--
dwmw2
next prev parent reply other threads:[~2001-08-07 9:37 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
2001-08-07 9:42 ` David Woodhouse [this message]
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=32062.997177378@redhat.com \
--to=dwmw2@infradead.org \
--cc=juan@hispafuentes.com \
--cc=linux-mtd@lists.infradead.org \
--cc=olea@hispafuentes.com \
--cc=vipin@embeddedlinuxworks.com \
/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