public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Vitaly Wool <vwool@ru.mvista.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH/RFC] remove len/ooblen confusion in MTD/NAND code: respin
Date: Tue, 07 Nov 2006 18:20:53 +0200	[thread overview]
Message-ID: <1162916453.5628.2.camel@sauron> (raw)
In-Reply-To: <20061103182038.f528d960.vwool@ru.mvista.com>

Hello Vitaly,
On Fri, 2006-11-03 at 18:20 +0300, Vitaly Wool wrote:
> Hello folks,
> 
> as was discussed between Ricard Wanderlof, David Woodhouse, Artem Bityutskiy and me, the current API for reading/writing OOB is confusing. The thing that introduces confusion is the need to specify ops.len together with ops.ooblen for reads/writes that concern only OOB not data area. So, ops.len is overloaded: when ops.datbuf != NULL it serves to specify the length of the data read, and when ops.datbuf == NULL, it serves to specify the full OOB read length.
> The patch inlined below is the slightly updated version of the previous patch serving the same purpose, but with the new Artem's comments taken into account.
> Artem, BTW, thanks a lot for your valuable input!

this patch does not apply to mtd-2.6.git:

patching file drivers/mtd/inftlcore.c
patching file drivers/mtd/nand/nand_base.c
Hunk #2 succeeded at 1006 (offset -1 lines).
Hunk #4 succeeded at 1260 (offset -1 lines).
Hunk #5 succeeded at 1282 (offset -2 lines).
Hunk #6 succeeded at 1300 (offset -1 lines).
Hunk #7 succeeded at 1321 (offset -2 lines).
Hunk #8 succeeded at 1343 (offset -1 lines).
Hunk #9 FAILED at 1665.
Hunk #10 succeeded at 1724 (offset -3 lines).
Hunk #11 succeeded at 1765 (offset -2 lines).
Hunk #12 succeeded at 1784 (offset -3 lines).
1 out of 12 hunks FAILED -- saving rejects to file
drivers/mtd/nand/nand_base.c.rej
patching file drivers/mtd/mtdchar.c
patching file drivers/mtd/mtdconcat.c
patching file drivers/mtd/nand/nand_bbt.c
patching file drivers/mtd/nftlcore.c
patching file drivers/mtd/ssfdc.c
patching file fs/jffs2/wbuf.c
patching file drivers/mtd/mtdpart.c
patching file include/linux/mtd/mtd.h

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

  reply	other threads:[~2006-11-07 16:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-03 15:20 [PATCH/RFC] remove len/ooblen confusion in MTD/NAND code: respin Vitaly Wool
2006-11-07 16:20 ` Artem Bityutskiy [this message]
2006-11-08 11:33   ` Vitaly Wool
2006-11-10 14:28   ` Vitaly Wool
  -- strict thread matches above, loose matches on Subject: below --
2006-11-09 15:26 Vitaly Wool
2006-11-10  8:23 ` Artem Bityutskiy
2006-11-10 12:46   ` Vitaly Wool
2006-11-02  7:06 Vitaly Wool
2006-11-03  9:16 ` 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=1162916453.5628.2.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=vwool@ru.mvista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox