From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Frank <mhf@linuxmail.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
Wolfgang Glas <wolfgang.glas@ev-i.at>,
swsusp-devel@lists.sourceforge.net
Subject: Re: Fwd: [Swsusp-devel] Kernel 2.6 pm_send_all() issues.
Date: Wed, 11 Feb 2004 16:23:02 +1100 [thread overview]
Message-ID: <1076476981.866.82.camel@gaston> (raw)
In-Reply-To: <200402102343.06896.mhf@linuxmail.org>
On Wed, 2004-02-11 at 02:43, Michael Frank wrote:
> This question is probably better suited for LKML.
Get nVidia to fix their drivers. pm_send_all() stuff is deprecated
and isn't called on purpose. Some of the handlers for these old-style
calls were doing weird stuff I'd rather not do again ;)
Ben.
next prev parent reply other threads:[~2004-02-11 5:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 15:43 Fwd: [Swsusp-devel] Kernel 2.6 pm_send_all() issues Michael Frank
2004-02-11 5:23 ` Benjamin Herrenschmidt [this message]
2004-02-11 6:46 ` Stephen Hemminger
2004-02-12 18:49 ` Nils Rennebarth
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=1076476981.866.82.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhf@linuxmail.org \
--cc=swsusp-devel@lists.sourceforge.net \
--cc=wolfgang.glas@ev-i.at \
/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