From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Brownell <david-b@pacbell.net>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.10-rc3
Date: Sun, 05 Dec 2004 15:07:16 +1100 [thread overview]
Message-ID: <1102219637.18809.0.camel@gaston> (raw)
In-Reply-To: <200412041903.55583.david-b@pacbell.net>
> Why was that changed? Are you sure it's not just a bug higher up
> in the call stack? Classically(*), both suspend() and resume()
> methods are called in contexts that can sleep, so that's a big
> change I'd expect to impact other drivers too. In fact that'd
> explain a lot of other messages I saw reported on the list...
Yes, lots of drivers are expected to be able to schedule in suspend and
resume requests. If that was broken upstream, then this is a big BUG.
> - Dave
>
> (*) Since APM days if not before.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Benjamin Herrenschmidt <benh@kernel.crashing.org>
next prev parent reply other threads:[~2004-12-05 4:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-05 3:03 Linux 2.6.10-rc3 David Brownell
2004-12-05 4:07 ` Benjamin Herrenschmidt [this message]
2004-12-05 12:14 ` Russell King
-- strict thread matches above, loose matches on Subject: below --
2004-12-04 0:19 Linus Torvalds
2004-12-04 9:06 ` Soeren Sonnenburg
2004-12-04 17:06 ` Alex Romosan
2004-12-04 17:24 ` Ari Pollak
2004-12-04 17:40 ` Alex Romosan
2004-12-04 19:21 ` Ari Pollak
2004-12-04 21:17 ` Martin Josefsson
2004-12-04 21:37 ` Alex Romosan
2004-12-04 21:42 ` Martin Josefsson
2004-12-04 23:48 ` Paul Ionescu
2004-12-04 21:47 ` Giridhar Pemmasani
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=1102219637.18809.0.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=david-b@pacbell.net \
--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