From: Michael Schierl <schierlm@gmx.de>
To: Pavel Machek <pavel@suse.cz>,
linux-laptop@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [APM] Is this the correct way to fix suspend bug introduced in 2.6.0-test4?
Date: Thu, 29 Jan 2004 20:36:00 +0100 [thread overview]
Message-ID: <401960A0.55EC26AE@gmx.de> (raw)
In-Reply-To: 40195A95.C675952C@gmx.de
I wrote:
> Thanks. BTW: I did not get any response from Stephen Rothwell (the guy
> who is listed as maintainer for APM in the MAINTAINERS file). How long
> should I wait for a response? Or should I simply submit the patch to
> Andrew?
JFTR: Now this address bounced:
550_5.1.1_<fr@canb.auug.org.au>..._User_unknown/Giving_up_on_203.10.76.34./
Michael
next prev parent reply other threads:[~2004-01-29 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 19:50 [PATCH] [APM] Is this the correct way to fix suspend bug introduced in 2.6.0-test4? Michael Schierl
2004-01-28 17:46 ` Pavel Machek
2004-01-29 19:10 ` Michael Schierl
2004-01-29 19:36 ` Michael Schierl [this message]
2004-01-29 19:55 ` Pavel Machek
2004-01-29 23:00 ` Axel Boldt
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=401960A0.55EC26AE@gmx.de \
--to=schierlm@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-laptop@vger.kernel.org \
--cc=pavel@suse.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