From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux PM <linux-pm@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC/RFT][PATCH -mm 0/5] swsusp: userland interface (rev. 2)
Date: Sat, 7 Jan 2006 00:59:34 +0100 [thread overview]
Message-ID: <20060106235934.GA20399@elf.ucw.cz> (raw)
In-Reply-To: <200601070041.22497.rjw@sisk.pl>
Hi!
> > > > Perhaps it is time to get 1/4 and 3/4 into -mm? You get my signed-off
> > > > on them...
> > >
> > > OK, I'll prepare them in a while.
> >
> > Thanks.
>
> I had to remake the 3/4 a bit, as it depended on some changes to power.h
> and swsusp.c done in the 2/4. Nothing particularly invasive, basically some
> definitions go to power.h and some function headers change, but please
> have a look if the patch is still OK (appended).
Still ok :-).
> > If code is simpler, lets stick with misc. You have to obtain minor by
> > mailing device@lanana.org, see Doc*/devices.txt.
>
> OK, I'll try.
It should be easy.
> > Ok, lets keep it as it is. We can always rename file in future. [I
> > don't quite understand your reasons for movement, through. Highmem is
> > part of snapshot we need to make; it is saved in a very different way
> > than rest of memory, but that is implementation detail...]
>
> I'm seeing this a bit differently. In my view highmem is handled very much
> like devices: save_highmem() turns it "off", restore_highmem() turns it "on"
> back again, they are even called next to device_power_up/down().
Yes, I guess it is possible to view it like that, too.
BTW your "write 500MB to swap" hit mainline few hours
ago. Congratulations.
Pavel
--
Thanks, Sharp!
prev parent reply other threads:[~2006-01-06 23:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 22:40 [RFC/RFT][PATCH -mm 0/5] swsusp: userland interface (rev. 2) Rafael J. Wysocki
2006-01-04 22:47 ` [RFC/RFT][PATCH -mm 1/5] swsusp: swsusp: low level " Rafael J. Wysocki
2006-01-04 22:51 ` [RFC/RFT][PATCH -mm 2/5] swsusp: userland " Rafael J. Wysocki
2006-01-04 23:49 ` [linux-pm] " Greg KH
2006-01-05 0:18 ` Pavel Machek
2006-01-05 0:26 ` Greg KH
2006-01-05 0:54 ` Pavel Machek
2006-01-05 0:55 ` Pavel Machek
2006-01-05 23:34 ` Rafael J. Wysocki
2006-01-05 23:45 ` Greg KH
2006-01-04 22:53 ` [RFC/RFT][PATCH -mm 3/5] swsusp: separate swap-writing and reading code " Rafael J. Wysocki
2006-01-04 22:55 ` [RFC/RFT][PATCH -mm 4/5] swsusp: move highmem-handling code to swsusp.c " Rafael J. Wysocki
2006-01-04 22:56 ` [RFC/RFT][PATCH -mm 5/5] swsusp: userland interface documentation and config Rafael J. Wysocki
2006-01-05 1:05 ` [RFC/RFT][PATCH -mm 0/5] swsusp: userland interface (rev. 2) Pavel Machek
2006-01-05 23:30 ` Pavel Machek
2006-01-06 21:17 ` Rafael J. Wysocki
2006-01-06 22:44 ` Pavel Machek
2006-01-06 23:41 ` Rafael J. Wysocki
2006-01-06 23:59 ` Pavel Machek [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=20060106235934.GA20399@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@osdl.org \
--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