From: "Alexey, Korolev" <alexey.korolev@intel.com>
To: tglx@linutronix.de, linux-mtd@lists.infradead.org
Subject: Re: [PATCH] Fixup in NAND bad block management + fixofmisspring.(nand_base.c)
Date: Mon, 20 Mar 2006 17:06:45 +0300 [thread overview]
Message-ID: <441EB6F5.7020704@intel.com> (raw)
In-Reply-To: <1142181850.19916.507.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 361 bytes --]
Hello Thomas,
I appologize for delay. I was away on vacation.
I your point of view regarding BB mabnagement is clear.
Fixup of badblockpos is rather suitable.
There was another very small fix for a missprint in nand_base.c. I think
it shouldn't raise many objections.
If you don't have any would you please check in the patch below ?
Thanks,
Alexey
[-- Attachment #2: miss_print_fixup.diff --]
[-- Type: text/plain, Size: 355 bytes --]
diff -aur b/drivers/mtd/nand/nand_base.c c/drivers/mtd/nand/nand_base.c
--- b/drivers/mtd/nand/nand_base.c 2006-02-09 20:05:28.447558688 +0300
+++ c/drivers/mtd/nand/nand_base.c 2006-02-09 20:14:58.182945744 +0300
@@ -1700,7 +1710,7 @@
len += num;
fsbuf += num;
}
- ofs += mtd->oobavail;
+ ofs += mtd->oobsize;
}
return this->oob_buf;
}
prev parent reply other threads:[~2006-03-20 14:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 15:44 [PATCH] Fixup in NAND bad block management + fix of misspring . (nand_base.c) Alexey, Korolev
2006-02-08 16:05 ` [PATCH] Fixup in NAND bad block management + fix of misspring .(nand_base.c) Alexey, Korolev
2006-02-08 20:11 ` Vitaly Wool
2006-02-09 17:54 ` Alexey, Korolev
2006-03-12 15:18 ` Thomas Gleixner
2006-02-09 18:03 ` Alexey, Korolev
2006-02-10 6:52 ` Vitaly Wool
2006-02-20 10:53 ` Alexey, Korolev
2006-02-20 11:00 ` Thomas Gleixner
2006-02-20 11:56 ` [PATCH] Fixup in NAND bad block management + fix of misspring.(nand_base.c) Alexey, Korolev
2006-02-20 12:08 ` Vitaly Wool
2006-02-20 12:11 ` Thomas Gleixner
2006-03-02 17:29 ` [PATCH] Fixup in NAND bad block management + fix ofmisspring.(nand_base.c) Alexey, Korolev
2006-03-12 16:44 ` Thomas Gleixner
2006-03-20 14:06 ` Alexey, Korolev [this message]
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=441EB6F5.7020704@intel.com \
--to=alexey.korolev@intel.com \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/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