From: Thomas Gleixner <tglx@linutronix.de>
To: "Alexey, Korolev" <alexey.korolev@intel.com>
Cc: linux-mtd@lists.infradead.org, jwboyer@gmail.com,
Vitaly Wool <vwool@ru.mvista.com>
Subject: Re: [PATCH] Fixup in NAND bad block management + fix of misspring .(nand_base.c)
Date: Sun, 12 Mar 2006 16:18:57 +0100 [thread overview]
Message-ID: <1142176737.19916.463.camel@localhost.localdomain> (raw)
In-Reply-To: <43EB81CF.1000400@intel.com>
On Thu, 2006-02-09 at 20:54 +0300, Alexey, Korolev wrote:
> Hi Vitaly,
>
> Thanks a lot for feedback.
> I agree for most of your comments. I missed some lines when I was
> merging the patch to the latest snapshot. I corrected it. Here is the
> second version at the end of the letter. Your comments are welcome.
I still do not understand what this whole crap is for. This patch will
not make it anywhere.
As I said before, this problem can simply be solved by a check for the
manufacturer ID in nand_scan() and a small tweak of nand_default_bbt().
Your solution requires board driver support, but this is a chip level
not a board level problem.
tglx
next prev parent reply other threads:[~2006-03-12 15:19 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 [this message]
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 ` [PATCH] Fixup in NAND bad block management + fixofmisspring.(nand_base.c) Alexey, Korolev
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=1142176737.19916.463.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=alexey.korolev@intel.com \
--cc=jwboyer@gmail.com \
--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