All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andi Kleen <andi@firstfloor.org>,
	linux-kernel@vger.kernel.org, peterz@infradead.org,
	arnd@arndb.de
Subject: Re: Remove last BKL leftover: lock_depth
Date: Fri, 6 May 2011 23:19:25 +0200	[thread overview]
Message-ID: <20110506211925.GA20111@one.firstfloor.org> (raw)
In-Reply-To: <20110506141114.10795803.akpm@linux-foundation.org>

On Fri, May 06, 2011 at 02:11:14PM -0700, Andrew Morton wrote:
> On Fri,  6 May 2011 14:05:24 -0700
> Andi Kleen <andi@firstfloor.org> wrote:
> 
> > I noticed the BKL task->lock_depth field was there with various users.
> > But they all don't need it anymore because the BKL is gone.
> > Fix up all the users and then finally remove the field.
> > 
> > This patchkit only removes code.
> 
> Patches in Ingo's tree from Jon Corbet have done this removal.

Ok thanks.  I was wondering why noone had done it.

-Andi
-- 
ak@linux.intel.com -- Speaking for myself only.

      reply	other threads:[~2011-05-06 21:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06 21:05 Remove last BKL leftover: lock_depth Andi Kleen
2011-05-06 21:05 ` [PATCH 1/4] BKL: Remove BKL references in mutex code Andi Kleen
2011-05-06 21:05 ` [PATCH 2/4] SCHED: Remove BKL accounting from schedstats Andi Kleen
2011-05-07  8:16   ` Ingo Molnar
2011-05-06 21:05 ` [PATCH 3/4] SCHED: Don't use BKL count for idle preempt count initialization Andi Kleen
2011-05-06 21:05 ` [PATCH 4/4] Remove last BKL leftover: lock_depth Andi Kleen
2011-05-06 21:11 ` Andrew Morton
2011-05-06 21:19   ` Andi Kleen [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=20110506211925.GA20111@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.