From: Pavel Machek <pavel@ucw.cz>
To: Brannon Barrett Klopfer <bklopfer@stanford.edu>,
linux-kernel@vger.kernel.org
Subject: Re: Completely dead on resume (no caps lock, nada)
Date: Sun, 6 Aug 2006 23:16:22 +0000 [thread overview]
Message-ID: <20060806231621.GE4205@ucw.cz> (raw)
In-Reply-To: <20060804215957.GA7008@nineveh.rivenstone.net>
Hi!
> > Sorry to bug the entire list with such a vaugue post, but I'm not sure what
> > driver/subsystem is causing this problem. I'm sure you all are sick of "My
> > computer won't suspend, what do I do?" posts, but...well, my computer won't
> > suspend...
>
> If no one reports bugs, they don't get fixed.
>
> Pavel Machek <pavel@suse.cz> is the swsusp maintainer, and should
> have been CC'd on this, otherwise he'll probably never see it.
> Linux-kernel is a busy place. :-)
Actually I probably would see it, just a little later.
Also I'm maintainer for swsusp. I tend to look after s2ram, too, so
cc-ing me will not hurt, but I do not maintain it.
Best place to ask is probably suspend-devel mailing list at
sourceforge's suspend project.
> I know Mr. Machek wants swsusp bug reports filed in Bugzilla at
> http://bugzilla.kernel.org , so you should do that, and then send a
> follow up to this, CC'd to Pavel, with a bugzilla bug number.
Actually I prefer 'simple' bugs to go via mail to suspend-devel... and
keep bugzilla for 'interesting' issues.
Pavel
--
Thanks for all the (sleeping) penguins.
prev parent reply other threads:[~2006-08-06 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 19:56 Brannon Barrett Klopfer
2006-08-04 21:59 ` Joseph Fannin
2006-08-06 23:16 ` Pavel Machek [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=20060806231621.GE4205@ucw.cz \
--to=pavel@ucw.cz \
--cc=bklopfer@stanford.edu \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®