From: Arnd Bergmann <arnd@arndb.de>
To: Jonathan Corbet <corbet@lwn.net>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Neil Brown <neilb@suse.de>
Subject: Re: [PATCH] sched: get rid of lock_depth
Date: Tue, 26 Apr 2011 15:03:39 +0200 [thread overview]
Message-ID: <201104261503.39419.arnd@arndb.de> (raw)
In-Reply-To: <20110422111910.456c0e84@bike.lwn.net>
On Friday 22 April 2011, Jonathan Corbet wrote:
> Neil Brown pointed out that lock_depth somehow escaped the BKL removal
> work. Let's get rid of it now.
>
> Note that the perf scripting utilities still have a bunch of code for
> dealing with common_lock_depth in tracepoints; I have left that in place in
> case anybody wants to use that code with older kernels.
>
> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
I wonder how I missed that, I certainly had a patch for this in the
beginning, but must have dropped it from my series later on.
Acked-by: Arnd Bergmann <arnd@arndb.de>
prev parent reply other threads:[~2011-04-26 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 17:19 [PATCH] sched: get rid of lock_depth Jonathan Corbet
2011-04-25 10:13 ` [tip:sched/core] sched: Get " tip-bot for Jonathan Corbet
2011-04-26 13:03 ` Arnd Bergmann [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=201104261503.39419.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=neilb@suse.de \
/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