From: Nigel Cunningham <ncunningham@clear.net.nz>
To: trelane@digitasaru.net
Cc: Luke-Jr <luke7jr@yahoo.com>,
swsusp-devel <swsusp-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Swsusp-devel] Software Suspend 2.0
Date: Sat, 31 Jan 2004 19:56:07 +1300 [thread overview]
Message-ID: <1075532166.17727.41.camel@laptop-linux> (raw)
In-Reply-To: <20040131064757.GB7245@digitasaru.net>
Hi.
On Sat, 2004-01-31 at 19:48, Joseph Pingenot wrote:
> Coupla quick questions for you, while we're on the topic.
>
> I get lots of fails against 2.6.2-rc2-mm1; will the -rcX kernels
> be addressed, or will the patches only be against non-rc kernels?
> What about -mm kernels?
In the past I have only done patches against the 2.6.x kernels. I'm
thinking, however, of requesting space on kernel.org for patches against
-rcX and -mm kernels. You're the second person to ask. If I get asked
some more, I might do it :> (It's not that it's hard, just that it takes
time and today is my last day working on the code full time).
> Also, how does this differ from what is currently in the vanilla
> kernels?
The best way to answer that is to point to
http://swsusp.sourceforge.net/features.html.
Regards,
Nigel
--
Nigel Cunningham
495 St Georges Road South, Hastings 4201, New Zealand
Evolution (n): A hypothetical process whereby infinitely improbable events occur
with alarming frequency, order arises from chaos, and no one is given credit.
next prev parent reply other threads:[~2004-01-31 6:54 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 4:24 Software Suspend 2.0 Nigel Cunningham
2004-01-30 10:04 ` Måns Rullgård
2004-01-30 10:22 ` Nigel Cunningham
2004-01-30 10:25 ` Nigel Cunningham
2004-01-31 18:09 ` Micha Feigin
2004-02-05 0:47 ` Software Suspend 2.0 [for 2.6.2 resend] Hugang
2004-01-31 6:22 ` [Swsusp-devel] Software Suspend 2.0 Luke-Jr
2004-01-31 6:37 ` Nigel Cunningham
2004-01-31 6:48 ` Joseph Pingenot
2004-01-31 6:56 ` Nigel Cunningham [this message]
2004-01-31 7:16 ` Joseph Pingenot
2004-01-31 7:28 ` Nigel Cunningham
2004-01-31 7:38 ` Joseph Pingenot
2004-01-31 7:48 ` Nigel Cunningham
2004-01-31 8:32 ` Nigel Cunningham
2004-01-31 9:03 ` Prakash K. Cheemplavam
2004-01-31 9:08 ` Nigel Cunningham
2004-01-31 9:19 ` Prakash K. Cheemplavam
2004-01-31 9:51 ` Nigel Cunningham
2004-01-31 10:43 ` Prakash K. Cheemplavam
2004-01-31 10:48 ` Prakash K. Cheemplavam
2004-01-31 13:25 ` Måns Rullgård
2004-01-31 23:11 ` Joseph Pingenot
2004-01-31 22:15 ` Måns Rullgård
2004-02-01 0:26 ` Micha Feigin
2004-02-01 1:48 ` oops with 2.6.1-rc1 and rc-3 Prakash K. Cheemplavam
2004-02-01 2:54 ` Micha Feigin
2004-02-01 10:36 ` Prakash K. Cheemplavam
2004-02-01 11:37 ` Prakash K. Cheemplavam
2004-01-31 9:35 ` [Swsusp-devel] Software Suspend 2.0 Éric Brunet
2004-01-31 9:38 ` Nigel Cunningham
2004-01-31 7:22 ` Luke-Jr
2004-01-31 7:31 ` Nigel Cunningham
2004-01-31 8:09 ` Luke-Jr
2004-01-31 8:11 ` Luke-Jr
2004-01-31 8:18 ` Nigel Cunningham
2004-01-31 15:23 ` Sebastian Kugler
2004-02-01 7:08 ` Hugang
2004-02-02 17:01 ` swsusp2 on ppc [Re: Software Suspend 2.0] Marco Giordani
2004-02-03 1:37 ` Hugang
2004-02-03 12:07 ` Marco Giordani
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=1075532166.17727.41.camel@laptop-linux \
--to=ncunningham@clear.net.nz \
--cc=linux-kernel@vger.kernel.org \
--cc=luke7jr@yahoo.com \
--cc=swsusp-devel@lists.sourceforge.net \
--cc=trelane@digitasaru.net \
/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