From: Olaf Hering <olh@suse.de>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: update-comment-about-gzip-scratch-size.patch added to -mm tree
Date: Sat, 28 May 2005 00:15:16 +0200 [thread overview]
Message-ID: <20050527221516.GA8259@suse.de> (raw)
In-Reply-To: <200505280215.01241.adobriyan@gmail.com>
On Sat, May 28, Alexey Dobriyan wrote:
> On Saturday 28 May 2005 01:50, akpm@osdl.org wrote:
> > From: Olaf Hering <olh@suse.de>
> >
> > fix a comment about the array size.
>
> > --- 25/arch/ppc/boot/openfirmware/chrpmain.c~update-comment-about-gzip-scratch-size
> > +++ 25-akpm/arch/ppc/boot/openfirmware/chrpmain.c
>
> > #define SCRATCH_SIZE (128 << 10)
> >
> > -static char scratch[SCRATCH_SIZE]; /* 1MB of scratch space for gunzip */
> > +static char scratch[SCRATCH_SIZE]; /* 128k of scratch space for gunzip */
>
> How about this?
Better remove the comment.
Or replace it with an URL to /. where we annouce the existence of scratch space for gzip.
prev parent reply other threads:[~2005-05-27 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200505272149.j4RLnKZW011173@shell0.pdx.osdl.net>
2005-05-27 22:15 ` update-comment-about-gzip-scratch-size.patch added to -mm tree Alexey Dobriyan
2005-05-27 22:15 ` Olaf Hering [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=20050527221516.GA8259@suse.de \
--to=olh@suse.de \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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