From: Andrew Morton <akpm@linux-foundation.org>
To: "Miles Lane" <miles.lane@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.22-rc6-mm1 -- Problems with suspend/resume.
Date: Tue, 3 Jul 2007 21:04:26 -0700 [thread overview]
Message-ID: <20070703210426.9d1ec62f.akpm@linux-foundation.org> (raw)
In-Reply-To: <a44ae5cd0707032045wa35095dg794608c2fd6d6633@mail.gmail.com>
On Tue, 3 Jul 2007 20:45:41 -0700 "Miles Lane" <miles.lane@gmail.com> wrote:
> Should I not report stuff like this when it is
> generated after an OOPS?
All bets are off if the kernel has oopsed. Reboot, see if
the bug still happens without the earlier oops, perhaps.
prev parent reply other threads:[~2007-07-04 4:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 1:09 2.6.22-rc6-mm1 -- Problems with suspend/resume Miles Lane
2007-07-04 1:34 ` Andrew Morton
2007-07-04 3:45 ` Miles Lane
2007-07-04 4:04 ` Andrew Morton [this message]
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=20070703210426.9d1ec62f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
/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