From: Sebastian Kugler <sebas1@gmx.de>
To: ncunningham@users.sourceforge.net
Cc: swsusp-devel <swsusp-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Swsusp-devel] [PREVIEW] Announce: Software Suspend Core Patch 2.0 rc4.
Date: Fri, 16 Jan 2004 22:09:05 +0100 [thread overview]
Message-ID: <1074287344.3660.11.camel@dali> (raw)
In-Reply-To: <1074282072.5328.52.camel@laptop-linux>
On Fri, 2004-01-16 at 20:41, Nigel Cunningham wrote:
> - Fixed issues with preemption resulting in 'bad: scheduling while
> atomic' messages in 2.6.
Just gave it a shot. It works like a charm. :>
> Further documentation is to be added and one minor quirk addressed, but codewise, I'm wondering if
> this might be 2.0 by another name.
Looks really good, congrats, Nigel and everyone else.
regards,
sebas
- - - - - -
Magic is always the best solution, especially reliable magic.
next prev parent reply other threads:[~2004-01-16 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 19:41 [PREVIEW] Announce: Software Suspend Core Patch 2.0 rc4 Nigel Cunningham
2004-01-16 19:48 ` [Swsusp-devel] " Nigel Cunningham
2004-01-16 21:09 ` Sebastian Kugler [this message]
2004-01-16 21:35 ` Andreas Jellinghaus
2004-01-17 2:07 ` Nigel Cunningham
2004-01-18 18:29 ` 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=1074287344.3660.11.camel@dali \
--to=sebas1@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@users.sourceforge.net \
--cc=swsusp-devel@lists.sourceforge.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