public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: akpm@osdl.org
Cc: olh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: update-comment-about-gzip-scratch-size.patch added to -mm tree
Date: Sat, 28 May 2005 02:15:00 +0400	[thread overview]
Message-ID: <200505280215.01241.adobriyan@gmail.com> (raw)
In-Reply-To: <200505272149.j4RLnKZW011173@shell0.pdx.osdl.net>

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?



Remove incorrect size from comment. scratch size is defined two lines above.

Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>

--- linux-vanilla/arch/ppc/boot/openfirmware/chrpmain.c	2005-05-27 23:06:23.000000000 +0400
+++ linux-scratch/arch/ppc/boot/openfirmware/chrpmain.c	2005-05-28 02:08:54.000000000 +0400
@@ -39,7 +39,7 @@ char *avail_high;
 
 #define SCRATCH_SIZE	(128 << 10)
 
-static char scratch[SCRATCH_SIZE];	/* 1MB of scratch space for gunzip */
+static char scratch[SCRATCH_SIZE];	/* scratch space for gunzip */
 
 typedef void (*kernel_start_t)(int, int, void *, unsigned int, unsigned int);
 

       reply	other threads:[~2005-05-27 22:14 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 ` Alexey Dobriyan [this message]
2005-05-27 22:15   ` update-comment-about-gzip-scratch-size.patch added to -mm tree Olaf Hering

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=200505280215.01241.adobriyan@gmail.com \
    --to=adobriyan@gmail.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olh@suse.de \
    /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