From: Bernardo Innocenti <bernie@develer.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: TRIVIAL: Fix linux/mtd/nftl.h for user-space inclusion
Date: Tue, 01 Jun 2004 23:39:44 +0200 [thread overview]
Message-ID: <40BCF7A0.70203@develer.com> (raw)
In-Reply-To: <1086125112.4273.2.camel@localhost.localdomain>
David Woodhouse wrote:
>>The header nftl-user.h doesn't exist in neither
>>linux-2.6.6 and in the version of mtd-utils
>>imported in uClinux-dist (a rather old version,
>>I shall admit).
>
> nftl-user.h is in CVS, along with a version of the userspace tools which
> uses it.
Ok, I'll check it out from CVS and post a patch to
the uClinux-dev mailing-list adding this header in
user/mtd-utils.
Is it 100% binary-compatible with all kernels?
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/
next prev parent reply other threads:[~2004-06-01 21:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 20:15 TRIVIAL: Fix linux/mtd/nftl.h for user-space inclusion Bernardo Innocenti
2004-06-01 20:29 ` David Woodhouse
2004-06-01 21:13 ` Bernardo Innocenti
2004-06-01 21:25 ` David Woodhouse
2004-06-01 21:39 ` Bernardo Innocenti [this message]
2004-06-01 21:41 ` 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=40BCF7A0.70203@develer.com \
--to=bernie@develer.com \
--cc=dwmw2@infradead.org \
--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