public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Lunz <lunz@falooley.org>
To: "Rafael J\. Wysocki" <rjw@sisk.pl>
Cc: Pavel Machek <pavel@ucw.cz>, Andrew Morton <akpm@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@redhat.com>
Subject: Re: [PATCH -mm 5/6] mm: Print first block offset for swap areas
Date: Fri, 22 Sep 2006 10:13:47 -0400	[thread overview]
Message-ID: <20060922141346.GA28949@opus.vpn-dev.reflex> (raw)
In-Reply-To: <200609221257.12303.rjw@sisk.pl>

On Fri, Sep 22, 2006 at 12:57:11PM +0200, Rafael J. Wysocki wrote:
> This is filesystem-dependent.  AFAICT not all filesystems are supported
> by GRUB.

of course, but it shows the technique is viable. Grub is 
widespread, and if it's good enough for so many x86 users to boot with
then the same approach ought to be adequate for resume, no?

Jason

  reply	other threads:[~2006-09-22 14:13 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-20 19:20 [PATCH -mm 0/6] swsusp: Add support for swap files Rafael J. Wysocki
2006-09-20 19:31 ` [PATCH -mm 1/6] swsusp: Use device and offset to intentify swap areas Rafael J. Wysocki
2006-09-21 21:27   ` Pavel Machek
2006-09-20 19:34 ` [PATCH -mm 2/6] swsusp: Rearrange swap-handling code Rafael J. Wysocki
2006-09-21 21:28   ` Pavel Machek
2006-09-20 19:41 ` [PATCH -mm 3/6] swsusp: Use block device offsets to identify swap locations Rafael J. Wysocki
2006-09-21 21:30   ` Pavel Machek
2006-09-21 22:21     ` Rafael J. Wysocki
2006-09-20 19:46 ` [PATCH -mm 4/6] swsusp: Add resume_offset command line parameter Rafael J. Wysocki
2006-09-21 21:31   ` Pavel Machek
2006-09-21 22:18     ` Rafael J. Wysocki
2006-09-22 13:34       ` Pavel Machek
2006-09-20 19:54 ` [PATCH -mm 5/6] mm: Print first block offset for swap areas Rafael J. Wysocki
2006-09-21 21:32   ` Pavel Machek
2006-09-21 22:10     ` Dave Jones
2006-09-21 22:46       ` Rafael J. Wysocki
2006-09-21 23:58         ` Jason Lunz
2006-09-22 10:57           ` Rafael J. Wysocki
2006-09-22 14:13             ` Jason Lunz [this message]
2006-09-22 14:18               ` Pavel Machek
2006-09-22 14:35                 ` Jason Lunz
2006-09-22 14:37                   ` Pavel Machek
2006-09-22 14:32               ` Rafael J. Wysocki
2006-09-22 14:33                 ` Pavel Machek
2006-09-20 20:01 ` [PATCH -mm 6/6] swsusp: Document support for swap files Rafael J. Wysocki
2006-09-21 21:33   ` Pavel Machek
2006-09-22  1:01 ` [PATCH -mm 0/6] swsusp: Add " Nigel Cunningham
2006-09-22  5:23   ` Pavel Machek
2006-09-22 11:28     ` Rafael J. Wysocki
2006-09-22 22:18       ` Nigel Cunningham
2006-09-23 22:18         ` Rafael J. Wysocki
2006-09-23 22:49           ` Nigel Cunningham
2006-09-23 22:59             ` Pavel Machek
2006-09-23 23:24               ` Nigel Cunningham
  -- strict thread matches above, loose matches on Subject: below --
2006-09-23  9:57 [PATCH -mm] " Rafael J. Wysocki
2006-09-23 10:10 ` [PATCH -mm 5/6] mm: Print first block offset for swap areas Rafael J. Wysocki
2006-09-26 19:39   ` Andrew Morton
2006-09-26 20:13     ` Rafael J. Wysocki
2006-09-26 20:49       ` Andrew Morton
2006-09-26 21:04         ` Rafael J. Wysocki

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=20060922141346.GA28949@opus.vpn-dev.reflex \
    --to=lunz@falooley.org \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    /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