public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@clear.net.nz>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	swsusp-devel <swsusp-devel@lists.sourceforge.net>
Subject: Re: [Swsusp-devel] Re: Tainted: S
Date: Wed, 09 Jul 2003 08:09:49 +1200	[thread overview]
Message-ID: <1057694989.14496.20.camel@laptop-linux> (raw)
In-Reply-To: <20030708195325.GA2673@suse.de>

Ah ok. How about 'Z' then? (As in zzzzz).

Regards,

Nigel

On Wed, 2003-07-09 at 07:53, Dave Jones wrote:
> On Wed, Jul 09, 2003 at 07:22:08AM +1200, Nigel Cunningham wrote:
>  > With the latest prepatch for the 2.4 version of swsusp, I've made swsusp
>  > taint the kernel upon resume from a suspend-to-disk. Any oopses that
>  > occur afterwards will contain S as a third character (eg PFS).
>  
> 2.5 already uses 'S' to mark "out-of-spec SMP system".
> 
> 		Dave
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: Parasoft
> Error proof Web apps, automate testing & more.
> Download & eval WebKing and get a free book.
> www.parasoft.com/bulletproofapps
> _______________________________________________
> swsusp-devel mailing list
> swsusp-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/swsusp-devel
-- 
Nigel Cunningham
495 St Georges Road South, Hastings 4201, New Zealand

You see, at just the right time, when we were still powerless,
Christ died for the ungodly.
	-- Romans 5:6, NIV.


  reply	other threads:[~2003-07-08 19:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-08 19:22 Tainted: S Nigel Cunningham
2003-07-08 19:53 ` Dave Jones
2003-07-08 20:09   ` Nigel Cunningham [this message]
2003-07-08 20:21     ` [Swsusp-devel] " Dave Jones
2003-07-08 20:23       ` Tainted: Z (was Tainted: S) Nigel Cunningham

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=1057694989.14496.20.camel@laptop-linux \
    --to=ncunningham@clear.net.nz \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --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