public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: dwmw2@infradead.org (David Woodhouse)
To: linux-mtd@lists.infradead.org
Subject: [PATCH] Fix stack usage for amd_flash.c
Date: 14 Mar 2003 16:05:10 +0000	[thread overview]
Message-ID: <1047657910.14792.153.camel@passion.cambridge.redhat.com> (raw)
In-Reply-To: <20030314154642.GC27154@wohnheim.fh-wedel.de>

On Fri, 2003-03-14 at 15:46, Joern Engel wrote:
> Hi!
> 
> This patch reduces the stack usage of amd_flash_probe by a couple of
> kByte.

Urgh. That should never have been on the stack in the first place. Make
it static. The comment about being deallocated when the probe is done is
bogus -- where do we think we get the contents of the table from when
_entering_ the probe function anyway? It's elsewhere in the kernel
image.

>  The target of freeing the memory after probe should be reached
> with __initdata as well. Untested, though.
> 
> Is it ok to apply?

No. You can't make that __initdata because the functions which _call_ it
aren't __init. You can load map drivers (e.g. pcmcia) as modules which
try to probe for all kinds of chips.  

Also note that all but the CFI-based drivers are deprecated. We have
old-style probes which allow us to use the CFI back-end drivers with
non-CFI chips anyway.

> J?rn

Btw you're sending out 8-bit mail with charset 'unknown-8bit'. What
should be a ?? isn't.

-- 
dwmw2

  reply	other threads:[~2003-03-14 16:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-14 15:46 [PATCH] Fix stack usage for amd_flash.c Joern Engel
2003-03-14 16:05 ` David Woodhouse [this message]
2003-03-14 16:19   ` Joern Engel
2003-03-14 16:43     ` David Woodhouse
     [not found] <3C6BEE8B5E1BAC42905A93F13004E8AB01CAF576@mailse01.se.axis.com>
2003-03-17  8:47 ` David Woodhouse

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=1047657910.14792.153.camel@passion.cambridge.redhat.com \
    --to=dwmw2@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox