All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kyungmin Park <kyungmin.park@samsung.com>
To: Artem Bityutskiy <dedekind@infradead.org>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: OneNAND: Update OOB free table
Date: Tue, 26 Dec 2006 07:15:24 +0000 (GMT)	[thread overview]
Message-ID: <13713069.585721167117324099.JavaMail.weblogic@ep_ml29> (raw)


> > Now OneNAND don't support MTD_OOB_AUTO, but if the jffs2 supports the this one. I will support it.
> > I think it's more reasonable to handle oob in driver level instead of filesystem.

> I take care about this in JFFS, you take care in OneNAND, OK?

No problem. I will support it.

> > Actually, I'm not sure where's the right place. But if we don't touch the watchdong.
> > it will soft lockup when mounting the JFFS2 with big partition. (I just borrowed it from nand.)

> Anyway, you should not touch watchdog. You problem is fixed by adding
> cond_resched() at the right places. What you did - you shut up watchdog
> which screamed about a real error, instead of solving the error.

It looks good. and also it works well. I will commit it.

Thank you,
Kyungmin Park

             reply	other threads:[~2006-12-26  7:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-26  7:15 Kyungmin Park [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-12-22  1:52 OneNAND: Update OOB free table Kyungmin Park
2006-12-22  9:17 ` Artem Bityutskiy
2006-12-18  4:24 Kyungmin Park
2006-12-18 14:23 ` Artem Bityutskiy
2006-12-21 11:15 ` Artem Bityutskiy
2006-12-21 12:35   ` Artem Bityutskiy
2006-12-15  2:38 Kyungmin Park
2006-12-15  8:33 ` Timo Teras
2006-12-15 10:41 ` Artem Bityutskiy
2006-12-15 11:19   ` Timo Teras
2006-12-08  0:11 Kyungmin Park
2006-12-08  8:43 ` Timo Teras
2006-12-11 12:20 ` Timo Teras

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=13713069.585721167117324099.JavaMail.weblogic@ep_ml29 \
    --to=kyungmin.park@samsung.com \
    --cc=dedekind@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 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.