From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Pavel Machek <pavel@suse.cz>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: swsusp does not stop DMA properly during resume
Date: Wed, 21 Jan 2004 11:09:18 +1100 [thread overview]
Message-ID: <1074643756.793.52.camel@gaston> (raw)
In-Reply-To: <20040120235347.GE1234@elf.ucw.cz>
> Hmmm... yes, I'll need to fix that one. [Is there console semaphore in
> 2.6.1, or do I need to wait for 2.6.2 before I can do something with
> this?]
{acquire,release}_console_sem() is in. I just added the warnings.
I also added proper take/release of it in the kernel/power/console.c
code, so you shouldn't have to touch that part
Ben.
prev parent reply other threads:[~2004-01-21 0:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 22:46 swsusp does not stop DMA properly during resume Pavel Machek
2004-01-20 23:06 ` Andrew Morton
2004-01-20 23:08 ` Pavel Machek
2004-01-20 23:40 ` Benjamin Herrenschmidt
2004-01-20 23:53 ` Pavel Machek
2004-01-21 0:01 ` Andrew Morton
2004-01-21 0:05 ` Pavel Machek
2004-01-21 0:09 ` Benjamin Herrenschmidt [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=1074643756.793.52.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@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