From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Theodore Ts'o" <tytso@mit.edu>, Andrew Morton <akpm@zip.com.au>,
torvalds@transmeta.com,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Dealing with swsusp vs. pmdisk
Date: Sun, 14 Mar 2004 11:18:02 +1100 [thread overview]
Message-ID: <1079223482.1960.113.camel@gaston> (raw)
In-Reply-To: <20040313123620.GA3352@openzaurus.ucw.cz>
On Sat, 2004-03-13 at 23:36, Pavel Machek wrote:
> Hi!
>
> > > Pavel, what do you think of the swsusp2 patch, BTW? My biggest
> > > complaint about it is that since it's maintained outside of the
> > > kernel, it's constantly behind about 0.75 revisions behind the latest
> > > 2.6 release. The feature set of swsusp2, if they can ever get it
> > > completely bugfree(tm) is certainly impressive.
> >
> > I'd like it to be merged upstream too.
>
> Are we talking 2.6 or 2.7 here?
2.6. I don't see any problem merging it at this point as long as
it's not invasive (I haven't looked at the code though). If it's
self-contained, it's more/less like adding a driver.
Ben.
next prev parent reply other threads:[~2004-03-14 0:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-12 22:46 Dealing with swsusp vs. pmdisk Pavel Machek
2004-03-13 0:47 ` Theodore Ts'o
2004-03-13 2:51 ` Benjamin Herrenschmidt
2004-03-13 12:36 ` Pavel Machek
2004-03-13 22:19 ` Micha Feigin
2004-03-14 0:18 ` Benjamin Herrenschmidt [this message]
2004-03-14 0:37 ` Pavel Machek
2004-03-15 20:05 ` Nigel Cunningham
2004-03-16 0:01 ` Benjamin Herrenschmidt
2004-03-15 23:31 ` Nigel Cunningham
2004-03-16 1:40 ` Benjamin Herrenschmidt
2004-03-15 23:59 ` Nigel Cunningham
2004-03-16 10:09 ` Pavel Machek
2004-03-13 12:28 ` Pavel Machek
2004-03-15 23:17 ` Jan Rychter
2004-03-16 18:16 ` Kevin Fenzi, Kevin Fenzi
2004-03-18 10:21 ` Jan Rychter
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=1079223482.1960.113.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=torvalds@transmeta.com \
--cc=tytso@mit.edu \
/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