public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: Guillaume Boissiere <boissiere@attbi.com>
Cc: linux-kernel@vger.kernel.org,
	kernel-janitor-discuss@lists.sourceforge.net
Subject: Re: [STATUS 2.5]  May 1, 2002 (BKL status)
Date: Wed, 01 May 2002 08:06:35 -0700	[thread overview]
Message-ID: <3CD0047B.4060605@us.ibm.com> (raw)
In-Reply-To: <3CCFBB21.9046.7889B0D2@localhost>

Guillaume Boissiere wrote:
> There has also been a lot of work done by various people to 
> remove the BKL from many places, which leads to my question:
> does anyone has a URL with a list of all the places where the
> BKL should eventually be removed and who's working on it?
> 
> It seems like it would be most useful if someone was willing
> to maintain something like this, but it might be a lot of 
> work - I don't know how long the list would be...

I may not be the leading BKL expert, but I play one on TV :)

Perhaps one of the kernel-janitor people would like to assist me with 
this (cc'ing that list).  I'd be willing to keep a web page to list all 
current BKL uses and keep track of them as they are removed/added 
Perhaps a set of web pages which resemble the directory structure of the 
kernel tree would be helpful??

Here's a good question for kernel-janitor, and anyone else who's 
interested, what format describing BKL use would most encourage you to 
go and remove it?  We already have Rick Lindsley's Global spinlock list: 
  http://prdownloads.sourceforge.net/lse/locking_doc-2.4.16 .  The BKL 
use in there is somewhat dated, but might be a good start.

I have some awk scripts that I use on each new kernel release to check 
for new and removed uses of the BKL.  I can adapt these to start 
checking new BK changesets for BKL changes.

-- 
Dave Hansen
haveblue@us.ibm.com


  reply	other threads:[~2002-05-01 15:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-01 13:53 [STATUS 2.5] May 1, 2002 Guillaume Boissiere
2002-05-01 15:06 ` Dave Hansen [this message]
2002-05-02 11:10   ` [STATUS 2.5] May 1, 2002 (BKL status) Guillaume Boissiere
2002-05-01 20:19 ` [STATUS 2.5] May 1, 2002 Mike Fedyk
2002-05-01 21:38   ` Andrew Morton
2002-05-02  1:11     ` Stephen Lord
2002-05-02  3:14       ` Eric W. Biederman
2002-05-02  3:29         ` Stephen Lord

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=3CD0047B.4060605@us.ibm.com \
    --to=haveblue@us.ibm.com \
    --cc=boissiere@attbi.com \
    --cc=kernel-janitor-discuss@lists.sourceforge.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