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:43:30 +0000	[thread overview]
Message-ID: <1047660209.14792.211.camel@passion.cambridge.redhat.com> (raw)
In-Reply-To: <20030314161916.GA23161@wohnheim.fh-wedel.de>

On Fri, 2003-03-14 at 16:19, Joern Engel wrote:
> On Fri, 14 March 2003 16:05:10 +0000, David Woodhouse wrote:
> > On Fri, 2003-03-14 at 15:46, Joern Engel wrote:
> > 
> > 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.
> 
> Ok, done.
> Is the new patch ok?

I'd probably have left it where it was and had a one-line patch just
which made it static, to keep the size of the patch down and avoid
conflicts with people trying to add new chip idents -- but since I don't
want people adding new chip idents anyway I suppose that's fine.

> Right. But since 2.[567] is going towards 4k kernel stack, those
> drivers should be fixed or revomed. If you don't remove it, I'll try
> to fix it. :)

True. Thanks.

> > Btw you're sending out 8-bit mail with charset 'unknown-8bit'. What
> > should be a ?? isn't.
> 
> Correct. I noticed that my inline patches were getting screwed up
> somehow and played around with the character set. It turned out that
> lkml is converting my mails to QP, no matter what I do. So the
> solution appears to be to include the important people in TO|CC and
> ignore the QP problem.

It's not converting to QP for me. My response to you, for example,
returned via lkml with...
	Content-Type: text/plain; charset=UTF-8
	Content-Transfer-Encoding: 8bit

Er, on further investigation it seems that Evolution actually _sent_ it
QP, and it got converted _from_ QP to 8-bit somewhere en route. That's
just bizarre. 

-- 
dwmw2

  reply	other threads:[~2003-03-14 16:43 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
2003-03-14 16:19   ` Joern Engel
2003-03-14 16:43     ` David Woodhouse [this message]
     [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=1047660209.14792.211.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