linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Manish Katiyar" <mkatiyar@gmail.com>
To: dwmw2@infradead.org, linux-fsdevel@vger.kernel.org,
	linux-mtd@lists.infradead.org
Subject: [PATCH} : Fix compilation warnings in fs/jffs2/nodemgmt.c
Date: Mon, 27 Oct 2008 19:00:17 +0530	[thread overview]
Message-ID: <ea11fea30810270630x2740ceb3m58df4d0093a86fee@mail.gmail.com> (raw)

Below patch fixes the following compilation warnings :
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


Signed-off-by: Manish Katiyar <mkatiyar@gmail.com>
---
 fs/jffs2/nodemgmt.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/fs/jffs2/nodemgmt.c b/fs/jffs2/nodemgmt.c
index 0875b60..21a0529 100644
--- a/fs/jffs2/nodemgmt.c
+++ b/fs/jffs2/nodemgmt.c
@@ -261,9 +261,11 @@ static int jffs2_find_nextblock(struct jffs2_sb_info *c)

 	jffs2_sum_reset_collected(c->summary); /* reset collected summary */

+#ifdef CONFIG_JFFS2_FS_WRITEBUFFER
 	/* adjust write buffer offset, else we get a non contiguous write bug */
 	if (!(c->wbuf_ofs % c->sector_size) && !c->wbuf_len)
 		c->wbuf_ofs = 0xffffffff;
+#endif

 	D1(printk(KERN_DEBUG "jffs2_find_nextblock(): new nextblock =
0x%08x\n", c->nextblock->offset));

-- 
1.5.4.3


Thanks -
Manish

             reply	other threads:[~2008-10-27 13:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-27 13:30 Manish Katiyar [this message]
2008-10-29  8:01 ` [PATCH} : Fix compilation warnings in fs/jffs2/nodemgmt.c Paulius Zaleckas

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=ea11fea30810270630x2740ceb3m58df4d0093a86fee@mail.gmail.com \
    --to=mkatiyar@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).