public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kasper Sandberg <lkml@metanurb.dk>
To: Pavel Machek <pavel@suse.cz>
Cc: Thomas Maier <Thomas.Maier@uni-kassel.de>, linux-kernel@vger.kernel.org
Subject: Re: [Suspend2-announce] Nigel's work and the future of Suspend2.
Date: Thu, 09 Mar 2006 15:55:44 +0100	[thread overview]
Message-ID: <1141916144.1745.8.camel@localhost> (raw)
In-Reply-To: <20060309114556.GE2813@elf.ucw.cz>

On Thu, 2006-03-09 at 12:45 +0100, Pavel Machek wrote:
> > > > Mainline swsusp never worked for me and
> > > > so with you leaving I am tempted to leave Linux behind after more than
> > > > ten years and switch to that other OS that at least has working suspend
> > > > and resume.  
> > didnt work on my laptop either, or one of my friends where i tried..
> > however, swsusp2 does..
> 
> bugzilla IDs?
have none, and i know this is very bad, however i didnt feel like i had
any useful information to contribute, all i get is black screen, nothing
to syslog, i have no serial port on my laptop..
> 
> > > Your choice... But it would be more productive to read the docs, go to
> > > the latest kernel, and if it does not work there, file
> > > bugzilla.kernel.org report.
> > yeah well.. IMO merging suspend2 is more productive, as i see it, it has
> > no downsides as to software suspend as of now, except IA64 support, and
> > it has ALOT of upsides.
> 
> Except that suspend2 is not going to be merged, for variety of
> reasons. One of them is that noone is working on merging it...
> 
one of them being the operative word, afaik, nigel was unwilling to work
on the issues needed for merging for the reason that it wouldnt be
merged..

out of personal interrest, why is it that prevents suspend2 from being
merged?

> So yes, filling bugzilla entries would be more productive than flaming
> me.
my post wasnt flaming, and wasnt intended to do so either.
> 								Pavel


  reply	other threads:[~2006-03-09 14:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-07  0:05 Nigel's work and the future of Suspend2 Nigel Cunningham
2006-03-07 13:14 ` [Suspend2-announce] " Thomas Maier
2006-03-08 12:25   ` Pavel Machek
2006-03-08 17:45     ` Thomas Maier
2006-03-08 20:39       ` Rafael J. Wysocki
2006-03-18  6:08         ` Tom Marshall
2006-03-20  8:13           ` Stefan Seyfried
2006-03-20 13:24             ` Mark Lord
2006-03-08 20:41       ` Pavel Machek
2006-03-09 11:33     ` Kasper Sandberg
2006-03-09 11:45       ` Pavel Machek
2006-03-09 14:55         ` Kasper Sandberg [this message]
2006-03-05  0:37           ` Pavel Machek
2006-03-09 21:34           ` Nigel Cunningham
2006-03-09 22:41             ` Pavel Machek
2006-03-10  4:53               ` Kasper Sandberg
2006-03-07 19:50 ` Bill Davidsen
2006-03-08 18:59   ` Lee Revell
2006-03-08 23:34   ` Nigel Cunningham
2006-03-08 12:21 ` Pavel Machek
2006-03-08 12:27   ` Nigel Cunningham
2006-03-08 21:55 ` Joshua Kugler

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=1141916144.1745.8.camel@localhost \
    --to=lkml@metanurb.dk \
    --cc=Thomas.Maier@uni-kassel.de \
    --cc=linux-kernel@vger.kernel.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