From: Robert Richter <robert.richter@amd.com>
To: Tejun Heo <tj@kernel.org>
Cc: "oprofile-list@lists.sf.net" <oprofile-list@lists.sf.net>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2.6.36-rc7] oprofile: don't use flush_scheduled_work()
Date: Fri, 29 Oct 2010 12:03:38 +0200 [thread overview]
Message-ID: <20101029100338.GE5969@erda.amd.com> (raw)
In-Reply-To: <4CB85C4C.6080806@kernel.org>
On 15.10.10 09:51:08, Tejun Heo wrote:
> flush_scheduled_work() is deprecated and scheduled to be removed.
> sync_stop() currently cancels cpu_buffer works inside buffer_mutex and
> flushes the system workqueue outside. Instead, split end_cpu_work()
> into two parts - stopping further work enqueues and flushing works -
> and do the former inside buffer_mutex and latter outside.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
Patch applied to oprofile/urgent. Thanks Tejun.
-Robert
--
Advanced Micro Devices, Inc.
Operating System Research Center
prev parent reply other threads:[~2010-10-29 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 13:51 [PATCH v2.6.36-rc7] oprofile: don't use flush_scheduled_work() Tejun Heo
2010-10-15 13:53 ` Tejun Heo
2010-10-29 10:03 ` Robert Richter [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=20101029100338.GE5969@erda.amd.com \
--to=robert.richter@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oprofile-list@lists.sf.net \
--cc=tj@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