public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Nigel Cunningham <ncunningham@cyclades.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Free swap suspend from depending upon PageReserved.
Date: Wed, 5 Oct 2005 14:12:22 +0200	[thread overview]
Message-ID: <20051005121222.GA22580@elf.ucw.cz> (raw)
In-Reply-To: <1128506536.5514.13.camel@localhost>

Hi!

> Here's the patch we've previously discussed, which removes the
> dependancy of swap suspend on PageReserved.

This ends up in Linus' changelog, so "we've previously discussed"
is not okay here. Missing signed-off. What is benefit of this?

swsusp part looks okay, but will Andrew like the generic part? I guess
I'd prefer to postpone this one (unless we are last user of
PageReserved) -- I do not see too big benefit and there's potential
for breakage.

> @@ -353,7 +357,7 @@ static void __init pagetable_init (void)
>  #endif
>  }
>  
> -#ifdef CONFIG_SOFTWARE_SUSPEND
> +#ifdef CONFIG_PM
>  /*
>   * Swap suspend & friends need this for resume because things like the intel-agp
>   * driver might have split up a kernel 4MB mapping.

This is wrong, right? It 

> @@ -540,6 +544,7 @@ void __init mem_init(void)
>  	int codesize, reservedpages, datasize, initsize;
>  	int tmp;
>  	int bad_ppro;
> +	void * addr;

Please make it void *addr;.
								Pavel

-- 
if you have sharp zaurus hardware you don't need... you know my address

  reply	other threads:[~2005-10-05 12:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-05 10:02 [PATCH] Free swap suspend from depending upon PageReserved Nigel Cunningham
2005-10-05 12:12 ` Pavel Machek [this message]
2005-10-05 12:52   ` Nigel Cunningham
2005-10-05 12:54   ` Rafael J. Wysocki
2005-10-05 20:37     ` Nigel Cunningham

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=20051005121222.GA22580@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@cyclades.com \
    /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