mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Alexander Belyakov" <abelyako@googlemail.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: build issue #569 for v2.6.28-rc1-5-g23cf24c : 'struct jffs2_sb_info' has no member named 'wbuf_ofs'
Date: Mon, 27 Oct 2008 12:25:10 +0300	[thread overview]
Message-ID: <fe810cf0810270225p27ab00br474b46ddb275d1f5@mail.gmail.com> (raw)
In-Reply-To: <200810261652.18700.toralf.foerster@gmx.de>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 989 bytes --]

On Sun, Oct 26, 2008 at 6:52 PM, Toralf Förster <toralf.foerster@gmx.de> wrote:> Hello,>> the build (.config attached) failed, make ends with :> ...>  CC      fs/jffs2/nodemgmt.o> fs/jffs2/nodemgmt.c: In function 'jffs2_find_nextblock':> fs/jffs2/nodemgmt.c:265: error: 'struct jffs2_sb_info' has no member> named 'wbuf_ofs'> fs/jffs2/nodemgmt.c:265: error: 'struct jffs2_sb_info' has no member> named 'wbuf_len'> fs/jffs2/nodemgmt.c:266: error: 'struct jffs2_sb_info' has no member> named 'wbuf_ofs'> make[2]: *** [fs/jffs2/nodemgmt.o] Error 1> make[1]: *** [fs/jffs2] Error 2> make: *** [fs] Error 2>> The build was made with :> $>make randconfig; make clean; make>
There is a commit in MTD git fixing this build issuehttp://git.infradead.org/mtd-2.6.git?a=commit;h=f04de505e3fa322728d1a851e08bf7060b117743
Thank you,Alexanderÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

      reply	other threads:[~2008-10-27  9:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-26 15:52 Toralf Förster
2008-10-27  9:25 ` Alexander Belyakov [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=fe810cf0810270225p27ab00br474b46ddb275d1f5@mail.gmail.com \
    --to=abelyako@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=toralf.foerster@gmx.de \
    /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
all inboxes | Powered by JetHome®