From: Pavel Machek <pavel@ucw.cz>
To: hugang@soulinfo.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: software suspend patch [1/6]
Date: Sun, 9 Jan 2005 23:43:25 +0100 [thread overview]
Message-ID: <20050109224325.GE1353@elf.ucw.cz> (raw)
In-Reply-To: <20041129154307.GC4616@hugang.soulinfo.com>
Hi!
> > I can not merge anything before 2.6.10. As you have seen, I have quite
> > a lot of patches in my tree, and I do not want mix them with these...
> >
> > > device-tree.diff
> > > base from suspend2 with a little changed.
> >
> > I do not want this one.
> >
> > > core.diff
> > > 1: redefine struct pbe for using _no_ continuous as pagedir.
> >
> > Can I get this one as a separate diff?
>
> Here is it.
Do you have any updates? It would be nice to separate non-continuous
pagedir from speeding up check_pagedir?
...plus check_pagedir should really use PageNosaveFree flag instead of
allocating there own (big!) bitmaps. It should also make the code
simpler...
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2005-01-09 22:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-27 22:07 Suspend 2 merge linux
2004-11-27 22:25 ` Pavel Machek
2004-11-28 8:29 ` Wichert Akkerman
2004-11-28 11:37 ` Pavel Machek
2004-11-28 16:23 ` software suspend patch [1/6] hugang
2004-11-28 16:24 ` software suspend patch [2/6] hugang
2004-11-28 17:03 ` Pavel Machek
2004-11-28 16:24 ` software suspend patch [3/6] hugang
2004-11-28 16:25 ` software suspend patch [4/6] hugang
2004-11-28 17:08 ` Pavel Machek
2004-11-28 16:25 ` software suspend patch [5/6] hugang
2004-11-28 16:25 ` software suspend patch [1/6] hugang
2004-11-28 17:11 ` Pavel Machek
2004-12-02 20:56 ` Guido Guenther
2004-11-28 16:58 ` Pavel Machek
2004-11-29 15:43 ` hugang
2005-01-09 22:43 ` Pavel Machek [this message]
2005-01-11 2:01 ` hugang
2005-01-11 3:15 ` Pavel Machek
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=20050109224325.GE1353@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=hugang@soulinfo.com \
--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;
as well as URLs for NNTP newsgroup(s).