From: Andrew Morton <akpm@osdl.org>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org, mochel@digitalimplant.org
Subject: Re: swsusp: fix default and merge upstream?
Date: Tue, 17 Aug 2004 11:28:43 -0700 [thread overview]
Message-ID: <20040817112843.1e3dae58.akpm@osdl.org> (raw)
In-Reply-To: <20040817180313.GD19009@elf.ucw.cz>
Pavel Machek <pavel@suse.cz> wrote:
>
> Hi!
>
> > > Perhaps now is the right time to merge -mm swsusp up to Linus?
> >
> > I suppose so. The way to do that is for Pat to merge up the various
> > patches which are hanging around and then ask Linus to do the bk pull.
>
> -mm plus two patches I sent today works pretty much okay.
OK.
> Are they
> swsusp-related things in your tree that are not in patrick's bk?
Just a couple of patches:
mm-swsusp-make-sure-we-do-not-return-to-userspace-where-image-is-on-disk.patch
mm-swsusp-copy_page-is-harmfull.patch
> driver-tree changes (enums etc) are pretty much orthogonal and can go
> in anytime later.
>
> > What's the testing status of the new code in bk-power.patch?
>
> Works for me, some users reported success (after being advised to use
> "shutdown" method), and suse pulled it into internal tree and it got
> basic testing there by Stefan. I guess that counts like "pretty well
> tested".
OK. I'll integrate your most recent patches and will squirt everything at
Patrick.
next prev parent reply other threads:[~2004-08-17 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 11:11 swsusp: fix default and merge upstream? Pavel Machek
2004-08-17 17:47 ` Andrew Morton
2004-08-17 18:03 ` Pavel Machek
2004-08-17 18:28 ` Andrew Morton [this message]
2004-08-17 19:03 ` 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=20040817112843.1e3dae58.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=pavel@suse.cz \
/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