All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kyungmin Park <kyungmin.park@samsung.com>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: OneNAND git
Date: Wed, 10 Jan 2007 00:46:35 +0000 (GMT)	[thread overview]
Message-ID: <21706105.522821168389995301.JavaMail.weblogic@ep_ml20> (raw)

Hi,

I saw your tree. and please append the last patch, read-while-load in DDP handling.
also we have to add "[MTD] OneNAND: fix onenand_wait bug".

Then what's your opinion of JFFS2 patch?

    [JFFS2] Skip ECC position in NAND family flash

    In OneNAND it updates the spare ecc area automatically when write the
    cleanmark in spare area

I hope to commit this one, too

The remaing patches are following.

1. [MTD] OneNAND: add subpage write support
2. [JFFS2] fix wrong ref-flash_offset usage.

I wonder why don't you manage separate tree of OneNAND?
I think thres's no problem of the removal of cond_resched in OneNAND driver.
If you don't agree this one, I can revert it.

Thank you,
Kyungmin Park






------- Original Message -------
Sender : Artem Bityutskiy<dedekind@infradead.org> 
Date   : Jan 09, 2007 21:24
Title  : OneNAND git

Kyungmin,

please, look at my OneNAND tree here:
http://git.infradead.org/?p=users/dedekind/dedekind-onenand-mtd-2.6.git;a=summary

I do not have several of your patches there, but I excluded the ones I
think should not sit in this tree.

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




             reply	other threads:[~2007-01-10  0:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-10  0:46 Kyungmin Park [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-01-11  2:25 OneNAND git Kyungmin Park
     [not found] <846526.522131168389817787.JavaMail.weblogic@ep_ml20>
2007-01-10 13:18 ` Artem Bityutskiy
2007-01-09 12:24 Artem Bityutskiy

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=21706105.522821168389995301.JavaMail.weblogic@ep_ml20 \
    --to=kyungmin.park@samsung.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 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.