From: b32955@freescale.com (Huang Shijie)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] mtd: gpmi: add NAND write verify support
Date: Mon, 13 Aug 2012 10:35:14 +0800 [thread overview]
Message-ID: <502867E2.8020405@freescale.com> (raw)
In-Reply-To: <201208122114.46901.marex@denx.de>
? 2012?08?13? 03:14, Marek Vasut ??:
> Don't forget the malloc header and padding around malloc()'d space. So you're
> behind the 2 * PAGESIZE anyway.
>
sorry, I misunderstood your meaning. My meaning is even the SLUB maybe
costs some extra memory, it still save much memory
then we use the devm_kzalloc().
thanks
Huang Shijie
prev parent reply other threads:[~2012-08-13 2:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-12 2:07 [PATCH v4] mtd: gpmi: add NAND write verify support Huang Shijie
2012-08-11 14:10 ` Marek Vasut
2012-08-11 15:15 ` Huang Shijie
2012-08-12 19:14 ` Marek Vasut
2012-08-13 2:21 ` Huang Shijie
2012-08-13 2:35 ` Huang Shijie [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=502867E2.8020405@freescale.com \
--to=b32955@freescale.com \
--cc=linux-arm-kernel@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 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).