From: Oliver Neukum <oliver@neukum.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input <linux-input@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: lockdep report at resume
Date: Tue, 21 Apr 2009 15:59:41 +0200 [thread overview]
Message-ID: <200904211559.43497.oliver@neukum.org> (raw)
In-Reply-To: <alpine.LNX.2.00.0904211550280.13028@wotan.suse.de>
Am Dienstag 21 April 2009 15:51:16 schrieb Jiri Kosina:
> [ thanks for the analysis Johannes ... involving also Oliver here; really
> seems like a false positive to me ]
I think he's right. But as a matter of principle I'd like to see
flush_scheduled_work() avoided where possible, hence the patch.
Regards
Oliver
next prev parent reply other threads:[~2009-04-21 13:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 16:01 lockdep report at resume Johannes Berg
2009-02-11 12:03 ` Jiri Kosina
2009-02-11 14:33 ` Johannes Berg
2009-02-18 13:17 ` Johannes Berg
2009-03-20 8:12 ` Johannes Berg
2009-03-20 14:37 ` Jiri Kosina
2009-03-20 14:39 ` Johannes Berg
2009-03-23 9:29 ` Johannes Berg
2009-03-31 8:36 ` Jiri Kosina
2009-03-31 8:38 ` Johannes Berg
2009-03-31 8:40 ` Jiri Kosina
2009-03-31 8:42 ` Johannes Berg
2009-04-01 9:40 ` Johannes Berg
2009-04-01 10:00 ` Johannes Berg
2009-04-21 13:51 ` Jiri Kosina
2009-04-21 13:59 ` Oliver Neukum [this message]
2009-04-21 14:11 ` Jiri Kosina
2009-04-21 14:14 ` Oliver Neukum
2009-04-21 14:26 ` Johannes Berg
2009-05-05 12:47 ` Jiri Kosina
2009-05-08 10:25 ` Johannes Berg
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=200904211559.43497.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=rjw@sisk.pl \
/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;
as well as URLs for NNTP newsgroup(s).