From: Artem Bityutskiy <dedekind1@gmail.com>
To: Kevin Cernekee <cernekee@gmail.com>
Cc: linux-mtd@lists.infradead.org, dwmw2@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: Increase NAND_MAX_OOBSIZE from 128 to 256
Date: Wed, 05 May 2010 14:19:05 +0300 [thread overview]
Message-ID: <1273058345.3702.175.camel@localhost> (raw)
In-Reply-To: <e511d9573281d8376f800574fac2d72663e2d558@localhost.localdomain>
On Mon, 2010-05-03 at 21:20 -0700, Kevin Cernekee wrote:
> NAND_MAX_OOBSIZE needs to be increased to support newer parts with
> 218 or 224 byte spare areas. Tested with Samsung K9GAG08U0D.
>
> Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
Pushed to l2-mtd-2.6 / master
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Kevin Cernekee <cernekee@gmail.com>
Cc: dwmw2@infradead.org, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: Increase NAND_MAX_OOBSIZE from 128 to 256
Date: Wed, 05 May 2010 14:19:05 +0300 [thread overview]
Message-ID: <1273058345.3702.175.camel@localhost> (raw)
In-Reply-To: <e511d9573281d8376f800574fac2d72663e2d558@localhost.localdomain>
On Mon, 2010-05-03 at 21:20 -0700, Kevin Cernekee wrote:
> NAND_MAX_OOBSIZE needs to be increased to support newer parts with
> 218 or 224 byte spare areas. Tested with Samsung K9GAG08U0D.
>
> Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
Pushed to l2-mtd-2.6 / master
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-05-05 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 4:20 [PATCH] mtd: Increase NAND_MAX_OOBSIZE from 128 to 256 Kevin Cernekee
2010-05-04 4:20 ` Kevin Cernekee
2010-05-05 11:19 ` Artem Bityutskiy [this message]
2010-05-05 11:19 ` 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=1273058345.3702.175.camel@localhost \
--to=dedekind1@gmail.com \
--cc=cernekee@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.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.