From: David Woodhouse <dwmw2@infradead.org>
To: Brian Norris <norris@broadcom.com>
Cc: Kevin Cernekee <cernekee@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH 2/2] mtd: nand: Increase NAND_MAX_OOBSIZE
Date: Fri, 20 Aug 2010 22:38:42 +0100 [thread overview]
Message-ID: <1282340322.25239.137.camel@localhost> (raw)
In-Reply-To: <4C6EF36F.2080306@broadcom.com>
On Fri, 2010-08-20 at 14:28 -0700, Brian Norris wrote:
> For the MAX macros? I have no idea. There were comments there telling
> me to do this whenever newer chips are supported.
I was thinking of the nand_ecc_layout stuff, I think.
Perhaps these buffers should be dynamically allocated and we should
ditch the MAX macros altogether?
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2010-08-20 21:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 19:36 [PATCH 1/2] mtd: nand: Support new Toshiba SLC Brian Norris
2010-08-20 19:36 ` [PATCH 2/2] mtd: nand: Increase NAND_MAX_OOBSIZE Brian Norris
2010-08-20 19:43 ` David Woodhouse
2010-08-20 21:28 ` Brian Norris
2010-08-20 21:38 ` David Woodhouse [this message]
2010-08-30 12:27 ` [PATCH 1/2] mtd: nand: Support new Toshiba SLC 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=1282340322.25239.137.camel@localhost \
--to=dwmw2@infradead.org \
--cc=cernekee@gmail.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=norris@broadcom.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;
as well as URLs for NNTP newsgroup(s).