From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@zip.com.au>
Subject: Re: Applications segfault on evo n620c with 2.6.10
Date: Fri, 28 Jan 2005 10:09:23 +1100 [thread overview]
Message-ID: <1106867363.15826.29.camel@nigelcunningham> (raw)
In-Reply-To: <20050127230131.GC1679@elf.ucw.cz>
Hi.
On Fri, 2005-01-28 at 10:01, Pavel Machek wrote:
> Yes, it happened even in cases when machine was not ever suspended. I
> guess I should also add that kernel is "tainted: pavel", (that means I
> have my own patches in; but I really believe that my changes are not
> responsible).
I often believe that too ;>
Nigel
--
Nigel Cunningham
Software Engineer
Cyclades Corporation
http://cyclades.com
next prev parent reply other threads:[~2005-01-27 23:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 18:43 Applications segfault on evo n620c with 2.6.10 Pavel Machek
2005-01-27 22:57 ` Nigel Cunningham
2005-01-27 23:01 ` Pavel Machek
2005-01-27 23:09 ` Nigel Cunningham [this message]
2005-01-28 2:36 ` hugang
2005-01-28 10:11 ` Pierre Chifflier
2005-01-28 13:04 ` 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=1106867363.15826.29.camel@nigelcunningham \
--to=ncunningham@linuxmail.org \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.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