From: dedekind1@gmail.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v10] MTD: LPC32xx MLC NAND driver
Date: Sat, 30 Jun 2012 17:22:51 +0300 [thread overview]
Message-ID: <1341066171.2115.10.camel@koala> (raw)
In-Reply-To: <4FEEF1D0.5060404@antcom.de>
On Sat, 2012-06-30 at 14:32 +0200, Roland Stigge wrote:
> Hi Artem!
>
> Thanks for the notes!
>
> On 29/06/12 14:37, Artem Bityutskiy wrote:
> > Successfully built configuration
> > "arm-lpc32xx_defconfig,arm,arm-unknown-linux-gnueabi-", results:
> >
> > --- before_patching.log +++ after_patching.log @@ @@
> > +drivers/mtd/nand/lpc32xx_mlc.c: In function 'lpc32xx_nand_probe':
> > +drivers/mtd/nand/lpc32xx_mlc.c:679:10: warning: variable 'sr' set
> > but not used [-Wunused-but-set-variable]
> > +drivers/mtd/nand/lpc32xx_mlc.c:561:24: error: bad constant
> > expression [sparse]
>
> This is because sparse doesn't understand this local variable:
>
> uint8_t buf[mtd->writesize];
mtd->writesize is typically 2048KiB (or even larger, there are MLCs with
4 and 8 KiB NAND page size). You cannot allocate that much on the stack,
linux kernel stack size is very small - only 8KiB, and there are people
who use even 4KiB stacks. So this have to be fixed.
> The above construction is quite convenient for this case and I'd
> prefer this to allocating another buffer dynamically.
Yes, in userspaces it is, but unfortunately in the kernel we cannot
afford allocating that much on the stack.
--
Best Regards,
Artem Bityutskiy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120630/af484b3c/attachment.sig>
prev parent reply other threads:[~2012-06-30 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 21:55 [PATCH v10] MTD: LPC32xx MLC NAND driver Roland Stigge
2012-06-29 12:37 ` Artem Bityutskiy
2012-06-29 12:56 ` Alexandre Pereira da Silva
2012-06-29 13:04 ` Artem Bityutskiy
2012-06-29 13:13 ` Alexandre Pereira da Silva
2012-06-30 12:32 ` Roland Stigge
2012-06-30 14:22 ` Artem Bityutskiy [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=1341066171.2115.10.camel@koala \
--to=dedekind1@gmail.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).