From: bandwidthcrunch <bandwidthcrunch@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: Re: jffs2 and 2.4.19
Date: Thu, 28 Oct 2004 10:39:03 +0530 [thread overview]
Message-ID: <b4618e0f04102722097014430f@mail.gmail.com> (raw)
In-Reply-To: <b4618e0f041027220032c8a576@mail.gmail.com>
gotcha , copying the mtd/include/linux/jffs2 and jffs2_fs_sb.h to
linux/include/linux solved it :)
On Thu, 28 Oct 2004 10:30:28 +0530, bandwidthcrunch
<bandwidthcrunch@gmail.com> wrote:
> Hi all,
> I have been trying to integrate a Jul 31 2002 snapshot of mtd
> into the 2.4.19 kernel but end up having
> file.c: In function `jffs2_fsync':
> file.c:33: structure has no member named `wbuf'
> file.c:33: structure has no member named `wbuf_len'
>
> Now i have in the earlier
> http://mhonarc.axis.se/jffs-dev/msg01282.html mail which says this
> happens due to CONFIG_JFFS2_FS being enabled in the kernel .
> But removing this is like disabling jffs2 support in the kernel ( yeah
> it builds the/fs/jffs2 modules ) . Isnt there a solution to this ?Any
> comments welcome
>
> regards,
> Band
>
prev parent reply other threads:[~2004-10-28 5:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 5:00 jffs2 and 2.4.19 bandwidthcrunch
2004-10-28 5:09 ` bandwidthcrunch [this message]
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=b4618e0f04102722097014430f@mail.gmail.com \
--to=bandwidthcrunch@gmail.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