All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: Linux mtd <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] [MTD] [NAND]: nand_default_mark_blockbad() doesn't work when flash-based bbt not enabled
Date: Fri, 20 Oct 2006 18:51:18 +0300	[thread overview]
Message-ID: <1161359478.3260.155.camel@sauron> (raw)
In-Reply-To: <Pine.LNX.4.64.0610201728220.25906@lnxricardw.se.axis.com>

On Fri, 2006-10-20 at 17:36 +0200, Ricard Wanderlof wrote:
>   		ofs += mtd->oobsize;
> -		chip->ops.len = 2;
> +		chip->ops.ooblen = 2;
>   		chip->ops.datbuf = NULL;
>   		chip->ops.oobbuf = buf;
>   		chip->ops.ooboffs = chip->badblockpos & ~0x01;

What is len and ooblen? Who initializes len then? I see len is used
later on.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2006-10-20 15:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-20 15:36 [PATCH] [MTD] [NAND]: nand_default_mark_blockbad() doesn't work when flash-based bbt not enabled Ricard Wanderlof
2006-10-20 15:51 ` Artem Bityutskiy [this message]
2006-10-20 19:00   ` Ricard Wanderlof
  -- strict thread matches above, loose matches on Subject: below --
2006-10-23  7:33 [PATCH] [MTD] [NAND]: nand_default_mark_blockbad() doesn't work when flash-based bbt not enabled (fwd) Ricard Wanderlof
2006-10-23  9:52 ` David Woodhouse
2006-10-23 10:46   ` [PATCH] [MTD] [NAND]: nand_default_mark_blockbad() doesn't work when flash-based bbt not enabled Ricard Wanderlof
2006-10-24  9:35   ` [PATCH] [MTD] [NAND]: nand_default_mark_blockbad() doesn't work when flash-based bbt not enabled (fwd) Vitaly Wool
2006-10-26  8:52     ` [PATCH] [MTD] [NAND]: nand_default_mark_blockbad() doesn't work when flash-based bbt not enabled Ricard Wanderlof
2006-10-26  8:55       ` Vitaly Wool
2006-10-26  9:06         ` Ricard Wanderlof

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=1161359478.3260.155.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=ricard.wanderlof@axis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.