From: Josh Triplett <josh@joshtriplett.org>
To: Huang Shijie <shijie8@gmail.com>
Cc: s.hauer@pengutronix.de, akinobu.mita@gmail.com,
linux-mtd@lists.infradead.org, computersforpeace@gmail.com,
dwmw2@infradead.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/4] mtd: kill the NAND_MAX_PAGESIZE/NAND_MAX_OOBSIZE
Date: Fri, 20 Dec 2013 09:13:40 -0800 [thread overview]
Message-ID: <20131220171340.GB26163@leaf> (raw)
In-Reply-To: <1387555350-989-1-git-send-email-shijie8@gmail.com>
On Sat, Dec 21, 2013 at 12:02:26AM +0800, Huang Shijie wrote:
> [1] Why kill them?
> As time goes on, the NAND's page size and oob size become larger and larger.
> So we have changes these two macros frequently in order to support the new
> NAND.
>
> [2] How does this patch set do?
> There are three drivers which uses these two macros, the mxc-nand, denali,
> and the cafe-nand.
>
> This patch will allocate a temporary buffer for the nand_scan_ident, and
> after it have getten the right page size and oob size, it will re-allocate
> the buffer again.
>
> [3] I do not have the boards which have the relative NAND controller.
>
> I hope someone can test this patch set.
>
> thanks.
>
>
> Huang Shijie (4):
> mtd: mxc-nand: kill the NAND_MAX_PAGESIZE/NAND_MAX_OOBSIZE
> mtd: denali: kill the NAND_MAX_PAGESIZE/NAND_MAX_OOBSIZE
> mtd: nand: kill the the NAND_MAX_PAGESIZE/NAND_MAX_OOBSIZE for
> nand_buffers{}
> mtd: nand: remove the NAND_MAX_PAGESIZE/NAND_MAX_OOBSIZE
For all four patches:
Reviewed-by: Josh Triplett <josh@joshtriplett.org>
WARNING: multiple messages have this Message-ID (diff)
From: josh@joshtriplett.org (Josh Triplett)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] mtd: kill the NAND_MAX_PAGESIZE/NAND_MAX_OOBSIZE
Date: Fri, 20 Dec 2013 09:13:40 -0800 [thread overview]
Message-ID: <20131220171340.GB26163@leaf> (raw)
In-Reply-To: <1387555350-989-1-git-send-email-shijie8@gmail.com>
On Sat, Dec 21, 2013 at 12:02:26AM +0800, Huang Shijie wrote:
> [1] Why kill them?
> As time goes on, the NAND's page size and oob size become larger and larger.
> So we have changes these two macros frequently in order to support the new
> NAND.
>
> [2] How does this patch set do?
> There are three drivers which uses these two macros, the mxc-nand, denali,
> and the cafe-nand.
>
> This patch will allocate a temporary buffer for the nand_scan_ident, and
> after it have getten the right page size and oob size, it will re-allocate
> the buffer again.
>
> [3] I do not have the boards which have the relative NAND controller.
>
> I hope someone can test this patch set.
>
> thanks.
>
>
> Huang Shijie (4):
> mtd: mxc-nand: kill the NAND_MAX_PAGESIZE/NAND_MAX_OOBSIZE
> mtd: denali: kill the NAND_MAX_PAGESIZE/NAND_MAX_OOBSIZE
> mtd: nand: kill the the NAND_MAX_PAGESIZE/NAND_MAX_OOBSIZE for
> nand_buffers{}
> mtd: nand: remove the NAND_MAX_PAGESIZE/NAND_MAX_OOBSIZE
For all four patches:
Reviewed-by: Josh Triplett <josh@joshtriplett.org>
next prev parent reply other threads:[~2013-12-20 17:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 16:02 [PATCH 0/4] mtd: kill the NAND_MAX_PAGESIZE/NAND_MAX_OOBSIZE Huang Shijie
2013-12-20 16:02 ` Huang Shijie
2013-12-20 16:02 ` [PATCH 1/4] mtd: mxc-nand: " Huang Shijie
2013-12-20 16:02 ` Huang Shijie
2013-12-20 16:02 ` [PATCH 2/4] mtd: denali: " Huang Shijie
2013-12-20 16:02 ` Huang Shijie
2013-12-20 16:02 ` [PATCH 3/4] mtd: nand: kill the the NAND_MAX_PAGESIZE/NAND_MAX_OOBSIZE for nand_buffers{} Huang Shijie
2013-12-20 16:02 ` Huang Shijie
2014-01-11 23:39 ` Brian Norris
2014-01-11 23:39 ` Brian Norris
2014-01-11 23:43 ` Russell King - ARM Linux
2014-01-11 23:43 ` Russell King - ARM Linux
2014-01-12 0:04 ` Brian Norris
2014-01-12 0:04 ` Brian Norris
2014-01-13 6:27 ` [PATCH fix] " Huang Shijie
2014-01-13 6:27 ` Huang Shijie
2014-01-29 0:23 ` Brian Norris
2014-01-29 0:23 ` Brian Norris
2013-12-20 16:02 ` [PATCH 4/4] mtd: nand: remove the NAND_MAX_PAGESIZE/NAND_MAX_OOBSIZE Huang Shijie
2013-12-20 16:02 ` Huang Shijie
2014-01-29 0:23 ` Brian Norris
2014-01-29 0:23 ` Brian Norris
2013-12-20 17:13 ` Josh Triplett [this message]
2013-12-20 17:13 ` [PATCH 0/4] mtd: kill " Josh Triplett
2014-01-11 23:47 ` Brian Norris
2014-01-11 23:47 ` Brian Norris
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=20131220171340.GB26163@leaf \
--to=josh@joshtriplett.org \
--cc=akinobu.mita@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
--cc=shijie8@gmail.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 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.